List Info

Thread: Created: (JBSEAM-2338) allow seam-gen to manage multiple projects




Created: (JBSEAM-2338) allow seam-gen to manage multiple projects
country flaguser name
United States
2007-12-03 13:28:51
allow seam-gen to manage multiple projects
------------------------------------------

                 Key: JBSEAM-2338
                 URL: http://
jira.jboss.com/jira/browse/JBSEAM-2338
             Project: JBoss Seam
          Issue Type: Feature Request
          Components: Tools
    Affects Versions: 2.0.0.GA
            Reporter: Dan Allen
         Assigned To: Dan Allen
             Fix For: 2.0.1.GA


Currently seam-gen only has the ability to manage one
project at a time. This limitation is due to the fact that
it sources build.properties from the seam-gen directory to
read settings about the managed project. I propose that we
make the name of the settings file dynamic so that it is
possible for seam-gen to select it based on the name of a
property supplied to the command line.

Example:

./seam -Dbuild=projecta explode
./seam explode

The first command would source build-projecta.properties.
The second command would fall back to the existing behavior
and source build.properties.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the
administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atl
assian.com/software/jira

        
_______________________________________________
jbossseam-issues mailing list
jbossseam-issueslists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossseam-issu
es

Updated: (JBSEAM-2338) allow seam-gen to manage multiple projects
country flaguser name
United States
2007-12-03 13:30:51
     [ http://jira.jboss.com/jira/browse/JBSEAM-2338?page=all
]

Dan Allen updated JBSEAM-2338:
------------------------------

    Attachment: JBSEAM-2338-v1.txt

Sets the property named "properties" to the
location of the build.properties file based on the value of
the property named "build".
Replaced all hardcoded references to build.properties with
$

> allow seam-gen to manage multiple projects
> ------------------------------------------
>
>                 Key: JBSEAM-2338
>                 URL: http://
jira.jboss.com/jira/browse/JBSEAM-2338
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Tools
>    Affects Versions: 2.0.0.GA
>            Reporter: Dan Allen
>         Assigned To: Dan Allen
>             Fix For: 2.0.1.GA
>
>         Attachments: JBSEAM-2338-v1.txt
>
>   Original Estimate: 10 minutes
>  Remaining Estimate: 10 minutes
>
> Currently seam-gen only has the ability to manage one
project at a time. This limitation is due to the fact that
it sources build.properties from the seam-gen directory to
read settings about the managed project. I propose that we
make the name of the settings file dynamic so that it is
possible for seam-gen to select it based on the name of a
property supplied to the command line.
> Example:
> ./seam -Dbuild=projecta explode
> ./seam explode
> The first command would source
build-projecta.properties. The second command would fall
back to the existing behavior and source build.properties.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the
administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atl
assian.com/software/jira

        
_______________________________________________
jbossseam-issues mailing list
jbossseam-issueslists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossseam-issu
es

Commented: (JBSEAM-2338) allow seam-gen to manage multiple projects
country flaguser name
United States
2007-12-03 13:36:51
    [ http://jira.jboss.com/jira/browse/JBS
EAM-2338?page=comments#action_12390334 ] 
            
Max Andersen commented on JBSEAM-2338:
--------------------------------------

shouldn't seam gen not just have a pointer to the
"current dir" and otherwise just ask for it?

I never understood why seamgen has project specific info in
its build.properties.


> allow seam-gen to manage multiple projects
> ------------------------------------------
>
>                 Key: JBSEAM-2338
>                 URL: http://
jira.jboss.com/jira/browse/JBSEAM-2338
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Tools
>    Affects Versions: 2.0.0.GA
>            Reporter: Dan Allen
>         Assigned To: Dan Allen
>             Fix For: 2.0.1.GA
>
>         Attachments: JBSEAM-2338-v1.txt
>
>   Original Estimate: 10 minutes
>  Remaining Estimate: 10 minutes
>
> Currently seam-gen only has the ability to manage one
project at a time. This limitation is due to the fact that
it sources build.properties from the seam-gen directory to
read settings about the managed project. I propose that we
make the name of the settings file dynamic so that it is
possible for seam-gen to select it based on the name of a
property supplied to the command line.
> Example:
> ./seam -Dbuild=projecta explode
> ./seam explode
> The first command would source
build-projecta.properties. The second command would fall
back to the existing behavior and source build.properties.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the
administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atl
assian.com/software/jira

        
_______________________________________________
jbossseam-issues mailing list
jbossseam-issueslists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossseam-issu
es

Commented: (JBSEAM-2338) allow seam-gen to manage multiple projects
country flaguser name
United States
2007-12-03 14:17:06
    [ http://jira.jboss.com/jira/browse/JBS
EAM-2338?page=comments#action_12390335 ] 
            
Dan Allen commented on JBSEAM-2338:
-----------------------------------

I see what you are saying. Part of the issue is that the
generated project does not store the settings that were used
by seam-gen in the project itself. I mean, the information
is there, it's just scattered throughout the configuration
files (as it was applied).

To me, this is one of those cases where it is easy to add
the flexibility to what exists, but long term perhaps there
is a bigger design change to be addressed. I don't like to
put small changes behind big ones, so my feeling is let's
give the option to get out of this hole first, then we can
decide how to get the settings out of the seam distribution
directory.

As I make this argument, my thought is shifting...it really
does make sense to get the build.properties file out of the
seam-gen directory. What sucks through is that you are going
to have to enter the whole path to the existing project. Ah,
but we could store "recently opened" projects and
have a menu system to select them by number. All I have to
say to that is *$# Ant. That would be a PITA to implement.

> allow seam-gen to manage multiple projects
> ------------------------------------------
>
>                 Key: JBSEAM-2338
>                 URL: http://
jira.jboss.com/jira/browse/JBSEAM-2338
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Tools
>    Affects Versions: 2.0.0.GA
>            Reporter: Dan Allen
>         Assigned To: Dan Allen
>             Fix For: 2.0.1.GA
>
>         Attachments: JBSEAM-2338-v1.txt
>
>   Original Estimate: 10 minutes
>  Remaining Estimate: 10 minutes
>
> Currently seam-gen only has the ability to manage one
project at a time. This limitation is due to the fact that
it sources build.properties from the seam-gen directory to
read settings about the managed project. I propose that we
make the name of the settings file dynamic so that it is
possible for seam-gen to select it based on the name of a
property supplied to the command line.
> Example:
> ./seam -Dbuild=projecta explode
> ./seam explode
> The first command would source
build-projecta.properties. The second command would fall
back to the existing behavior and source build.properties.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the
administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atl
assian.com/software/jira

        
_______________________________________________
jbossseam-issues mailing list
jbossseam-issueslists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossseam-issu
es

Commented: (JBSEAM-2338) allow seam-gen to manage multiple projects
country flaguser name
United States
2007-12-03 15:32:51
    [ http://jira.jboss.com/jira/browse/JBS
EAM-2338?page=comments#action_12390343 ] 
            
Pete Muir commented on JBSEAM-2338:
-----------------------------------

I don't understand why we don't store the main
seam-gen.properties in the created project, and then have a
say list of 1-5 recent projects in the properties file in
the seam-gen directory. User can then easily select from the
list or enter a new path.

> allow seam-gen to manage multiple projects
> ------------------------------------------
>
>                 Key: JBSEAM-2338
>                 URL: http://
jira.jboss.com/jira/browse/JBSEAM-2338
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Tools
>    Affects Versions: 2.0.0.GA
>            Reporter: Dan Allen
>         Assigned To: Dan Allen
>             Fix For: 2.0.1.GA
>
>         Attachments: JBSEAM-2338-v1.txt
>
>   Original Estimate: 10 minutes
>  Remaining Estimate: 10 minutes
>
> Currently seam-gen only has the ability to manage one
project at a time. This limitation is due to the fact that
it sources build.properties from the seam-gen directory to
read settings about the managed project. I propose that we
make the name of the settings file dynamic so that it is
possible for seam-gen to select it based on the name of a
property supplied to the command line.
> Example:
> ./seam -Dbuild=projecta explode
> ./seam explode
> The first command would source
build-projecta.properties. The second command would fall
back to the existing behavior and source build.properties.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the
administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atl
assian.com/software/jira

        
_______________________________________________
jbossseam-issues mailing list
jbossseam-issueslists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossseam-issu
es

Commented: (JBSEAM-2338) allow seam-gen to manage multiple projects
country flaguser name
United States
2007-12-03 15:32:51
    [ http://jira.jboss.com/jira/browse/JBS
EAM-2338?page=comments#action_12390342 ] 
            
Max Andersen commented on JBSEAM-2338:
--------------------------------------

does start with the simple thing first....just store the
default root dir plus projectname and source the pointed to
directory...just need to be specificed in a sepaerate file
to make sure you dont get stuck with possible left over
attributes from existing build.properties.

wont make it worse that it is today and simpler for the
future

> allow seam-gen to manage multiple projects
> ------------------------------------------
>
>                 Key: JBSEAM-2338
>                 URL: http://
jira.jboss.com/jira/browse/JBSEAM-2338
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Tools
>    Affects Versions: 2.0.0.GA
>            Reporter: Dan Allen
>         Assigned To: Dan Allen
>             Fix For: 2.0.1.GA
>
>         Attachments: JBSEAM-2338-v1.txt
>
>   Original Estimate: 10 minutes
>  Remaining Estimate: 10 minutes
>
> Currently seam-gen only has the ability to manage one
project at a time. This limitation is due to the fact that
it sources build.properties from the seam-gen directory to
read settings about the managed project. I propose that we
make the name of the settings file dynamic so that it is
possible for seam-gen to select it based on the name of a
property supplied to the command line.
> Example:
> ./seam -Dbuild=projecta explode
> ./seam explode
> The first command would source
build-projecta.properties. The second command would fall
back to the existing behavior and source build.properties.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the
administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atl
assian.com/software/jira

        
_______________________________________________
jbossseam-issues mailing list
jbossseam-issueslists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossseam-issu
es

Commented: (JBSEAM-2338) allow seam-gen to manage multiple projects
country flaguser name
United States
2007-12-03 15:45:04
    [ http://jira.jboss.com/jira/browse/JBS
EAM-2338?page=comments#action_12390348 ] 
            
Max Andersen commented on JBSEAM-2338:
--------------------------------------

makes sense.

..and advantage of having properties inside the project is
that jbosstools eventually will be able to reflect upon them
too!

> allow seam-gen to manage multiple projects
> ------------------------------------------
>
>                 Key: JBSEAM-2338
>                 URL: http://
jira.jboss.com/jira/browse/JBSEAM-2338
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Tools
>    Affects Versions: 2.0.0.GA
>            Reporter: Dan Allen
>         Assigned To: Dan Allen
>             Fix For: 2.0.1.GA
>
>         Attachments: JBSEAM-2338-v1.txt
>
>   Original Estimate: 10 minutes
>  Remaining Estimate: 10 minutes
>
> Currently seam-gen only has the ability to manage one
project at a time. This limitation is due to the fact that
it sources build.properties from the seam-gen directory to
read settings about the managed project. I propose that we
make the name of the settings file dynamic so that it is
possible for seam-gen to select it based on the name of a
property supplied to the command line.
> Example:
> ./seam -Dbuild=projecta explode
> ./seam explode
> The first command would source
build-projecta.properties. The second command would fall
back to the existing behavior and source build.properties.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the
administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atl
assian.com/software/jira

        
_______________________________________________
jbossseam-issues mailing list
jbossseam-issueslists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossseam-issu
es

Updated: (JBSEAM-2338) allow seam-gen to manage multiple projects
country flaguser name
United States
2007-12-11 21:52:59
     [ http://jira.jboss.com/jira/browse/JBSEAM-2338?page=all
]

Norman Richards updated JBSEAM-2338:
------------------------------------

    Fix Version/s: 2.0.1.GA
                       (was: 2.0.1.CR1)

> allow seam-gen to manage multiple projects
> ------------------------------------------
>
>                 Key: JBSEAM-2338
>                 URL: http://
jira.jboss.com/jira/browse/JBSEAM-2338
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Tools
>    Affects Versions: 2.0.0.GA
>            Reporter: Dan Allen
>         Assigned To: Dan Allen
>             Fix For: 2.0.1.GA
>
>         Attachments: JBSEAM-2338-v1.txt
>
>   Original Estimate: 10 minutes
>  Remaining Estimate: 10 minutes
>
> Currently seam-gen only has the ability to manage one
project at a time. This limitation is due to the fact that
it sources build.properties from the seam-gen directory to
read settings about the managed project. I propose that we
make the name of the settings file dynamic so that it is
possible for seam-gen to select it based on the name of a
property supplied to the command line.
> Example:
> ./seam -Dbuild=projecta explode
> ./seam explode
> The first command would source
build-projecta.properties. The second command would fall
back to the existing behavior and source build.properties.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the
administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atl
assian.com/software/jira

        
_______________________________________________
jbossseam-issues mailing list
jbossseam-issueslists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossseam-issu
es

Updated: (JBSEAM-2338) allow seam-gen to manage multiple projects
country flaguser name
United States
2007-12-19 13:34:44
     [ http://jira.jboss.com/jira/browse/JBSEAM-2338?page=all
]

Pete Muir updated JBSEAM-2338:
------------------------------

    Fix Version/s: 2.0.x
                       (was: 2.0.1.GA)

> allow seam-gen to manage multiple projects
> ------------------------------------------
>
>                 Key: JBSEAM-2338
>                 URL: http://
jira.jboss.com/jira/browse/JBSEAM-2338
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Tools
>    Affects Versions: 2.0.0.GA
>            Reporter: Dan Allen
>         Assigned To: Dan Allen
>             Fix For: 2.0.x
>
>         Attachments: JBSEAM-2338-v1.txt
>
>   Original Estimate: 10 minutes
>  Remaining Estimate: 10 minutes
>
> Currently seam-gen only has the ability to manage one
project at a time. This limitation is due to the fact that
it sources build.properties from the seam-gen directory to
read settings about the managed project. I propose that we
make the name of the settings file dynamic so that it is
possible for seam-gen to select it based on the name of a
property supplied to the command line.
> Example:
> ./seam -Dbuild=projecta explode
> ./seam explode
> The first command would source
build-projecta.properties. The second command would fall
back to the existing behavior and source build.properties.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the
administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atl
assian.com/software/jira

        
_______________________________________________
jbossseam-issues mailing list
jbossseam-issueslists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossseam-issu
es

Updated: (JBSEAM-2338) allow seam-gen to manage multiple projects
country flaguser name
United States
2008-02-11 12:59:57
     [ http://jira.jboss.com/jira/browse/JBSEAM-2338?page=all
]

Norman Richards updated JBSEAM-2338:
------------------------------------

    Fix Version/s: 2.1.0.GA
                       (was: 2.1.0.A1)

> allow seam-gen to manage multiple projects
> ------------------------------------------
>
>                 Key: JBSEAM-2338
>                 URL: http://
jira.jboss.com/jira/browse/JBSEAM-2338
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Tools
>    Affects Versions: 2.0.0.GA
>            Reporter: Dan Allen
>         Assigned To: Dan Allen
>             Fix For: 2.1.0.GA
>
>         Attachments: JBSEAM-2338-v1.txt
>
>   Original Estimate: 10 minutes
>  Remaining Estimate: 10 minutes
>
> Currently seam-gen only has the ability to manage one
project at a time. This limitation is due to the fact that
it sources build.properties from the seam-gen directory to
read settings about the managed project. I propose that we
make the name of the settings file dynamic so that it is
possible for seam-gen to select it based on the name of a
property supplied to the command line.
> Example:
> ./seam -Dbuild=projecta explode
> ./seam explode
> The first command would source
build-projecta.properties. The second command would fall
back to the existing behavior and source build.properties.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the
administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atl
assian.com/software/jira

        
_______________________________________________
jbossseam-issues mailing list
jbossseam-issueslists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossseam-issu
es

[1-10]

about | contact  Other archives ( Real Estate discussion Medical topics )