inline...
--- Henri Yandell [EMAIL PROTECTED] wrote:
On 3/2/06, Prasad Kashyap
[EMAIL PROTECTED] wrote:
Hmm.. somewhere up in this thread, someone had
mentioned that we
should do this as a bottoms-up approach where we
migrate the ones
without any deps (call it base modules) first and
2006/3/2, anita kulshreshtha [EMAIL PROTECTED]:
Prasad,
Thanks! The version no. for
geronimo-javamail_1.3.1_spec jar is 1.1-SNAPSHOT in
maven1 build and 1.2-SNAPSHOT in maven2 build. There
is a working pom.xml for naming-builder but it is not
in the modules list in the parent pom.xml (rev
2006/3/1, Dain Sundstrom [EMAIL PROTECTED]:
What does converted mean? Does it mean that all unit tests pass?
Yes. That's the absolute minimum to mark a module as converted.
How about conversion to the maven2 directory structure?
That's interesting question. Shall we do that [empty|now|at
2006/3/1, Prasad Kashyap [EMAIL PROTECTED]:
Dain, your wish has been granted. Here is a humble beginning
http://opensource2.atlassian.com/confluence/oss/display/GERONIMO/Migration+to+Maven2
Great work, Prasad! It's a pleasure to work with you and *try* to keep
your pace ;)
But...why do we get
Jacek, I couldn't agree more. That is exactly what we should be doing.
The devlist is a more happening place. So we should continue with all
the discussions here.
However, a lot of important decisions and information gets drowned in
the chatter here. So the wiki can be used to get a snapshot
2006/3/2, Prasad Kashyap [EMAIL PROTECTED]:
However, a lot of important decisions and information gets drowned in
the chatter here. So the wiki can be used to get a snapshot summary
status of the work in progress. This will be useful for folks who are
not really following this thread but yet
Jacek,
maven1 build puts jars in
.../.maven/repository/o/a/g/jars and poms in poms dir.
It would be nice if they could be written to
/.m2/repository/org/apache/geronimo in maven2
directory format. This would allow us to build any
single module using mvn. The jars for the modules that
have
Jacek, until we all agree on a tool that will capture the status, I'll
try my best to keep the confluence wiki updated.
It'd be nice if others could update the wiki too with their status and
issues. The confluence wiki is very easy to use. It's just like
editing a word document.
Cheers
Prasad
Having the two wikis is confusing; but definitely +1 on recording the
state of the migration in a wiki.
Hen
On 3/2/06, Prasad Kashyap [EMAIL PROTECTED] wrote:
Jacek, until we all agree on a tool that will capture the status, I'll
try my best to keep the confluence wiki updated.
It'd be nice
Hmm.. somewhere up in this thread, someone had mentioned that we
should do this as a bottoms-up approach where we migrate the ones
without any deps (call it base modules) first and then work up the
chain.
That will impose a sequential order on the migration effort and may
also possibly hold it
On 3/2/06, Prasad Kashyap [EMAIL PROTECTED] wrote:
Hmm.. somewhere up in this thread, someone had mentioned that we
should do this as a bottoms-up approach where we migrate the ones
without any deps (call it base modules) first and then work up the
chain.
That will impose a sequential order
On 3/2/06, Henri Yandell [EMAIL PROTECTED] wrote:
Anyone know if there's a way to get Maven to dump the transitive build
order from the project.xmls? That would indicate the order to fix in I
think.
Please ignore the idiot. Maven 1 does not have transitive builds :)
Hen
On Mar 2, 2006, at 10:00 AM, Henri Yandell wrote:
On 3/2/06, Henri Yandell [EMAIL PROTECTED] wrote:
Anyone know if there's a way to get Maven to dump the transitive
build
order from the project.xmls? That would indicate the order to fix
in I
think.
Please ignore the idiot. Maven 1
On 3/2/06, David Jencks [EMAIL PROTECTED] wrote:
On Mar 2, 2006, at 10:00 AM, Henri Yandell wrote:
On 3/2/06, Henri Yandell [EMAIL PROTECTED] wrote:
Anyone know if there's a way to get Maven to dump the transitive
build
order from the project.xmls? That would indicate the order to fix
On 3/1/06, Dain Sundstrom [EMAIL PROTECTED] wrote:
Cool.
What does converted mean?
Does it mean that all unit tests pass?
I'm presuming it means:
Red - No pom exists in SVN
Yellow - Pom exists in SVN, but mvn install fails
Green - Pom exists in SVN and a mvn install succeeds (compile/tests)
On 2/20/06, Jacek Laskowski [EMAIL PROTECTED] wrote:
2006/2/20, Gianny Damour [EMAIL PROTECTED]:
I think that this has already been suggested by David J.: we add a goal,
e.g. new000, which is executed between new00 and new1. new000 launches
mvn install in the root project directory. We add
It would be nice if we had a wiki page with a list of every module in
geronimo and the state of the conversion (e.g., compiles, tests pass,
directory structure changed...). This would really help those that
don't have time to follow the conversion process, like myself :)
-dain
On Mar 1,
Cool.
What does converted mean? Does it mean that all unit tests pass?
How about conversion to the maven2 directory structure?
-dain
On Mar 1, 2006, at 2:16 PM, Prasad Kashyap wrote:
Dain, your wish has been granted. Here is a humble beginning
Don't we also need to include migration of the configs in your table?
Joe
Prasad Kashyap wrote:
Dain, your wish has been granted. Here is a humble beginning
http://opensource2.atlassian.com/confluence/oss/display/GERONIMO/Migration+to+Maven2
Cheers
Prasad.
On 3/1/06, Dain Sundstrom [EMAIL
Prasad,
A minor correction.. Migration of tomcat and
tomcat-builder is a work in progress. I think a 'green
check/red X' mark instead of 'yes/no' in the
'converted' column would be more readable.
Thanks
Anita
--- Prasad Kashyap [EMAIL PROTECTED]
wrote:
Dain, your wish has been granted.
Dain,
Some of the tests in some modules have not been migrated.
http://www.mail-archive.com/dev@geronimo.apache.org/msg17958.html
https://issues.apache.org/jira/browse/GERONIMO-1629
Anders, I believe, writes -
Some builders uses jelly to assemble j2ee archives for testing
purposes. These tests
Anita, the yes|no seemed easy to generate then. I shall replace
those with some gifs soon.
Cheers
Prasad
On 3/1/06, anita kulshreshtha [EMAIL PROTECTED] wrote:
Prasad,
A minor correction.. Migration of tomcat and
tomcat-builder is a work in progress. I think a 'green
check/red X' mark
Prasad,
Thanks! The version no. for
geronimo-javamail_1.3.1_spec jar is 1.1-SNAPSHOT in
maven1 build and 1.2-SNAPSHOT in maven2 build. There
is a working pom.xml for naming-builder but it is not
in the modules list in the parent pom.xml (rev
382066).
Thanks
Anita
--- Prasad Kashyap [EMAIL
Jacek,
I had better luck later at night and was able to
build a dummy tomcat project. I have few questions :
1. The commons-modeler jar available at repos is
at 1.1M1. We currently use 1.1.
Should we change to 1.1M1?
2. Is anyone writing the assembly-plugin?
Thnaks
2006/2/28, anita kulshreshtha [EMAIL PROTECTED]:
Jacek,
I had better luck later at night and was able to
build a dummy tomcat project. I have few questions :
1. The commons-modeler jar available at repos is
at 1.1M1. We currently use 1.1.
Should we change to 1.1M1?
anita kulshreshtha wrote:
Jacek,
I had better luck later at night and was able to
build a dummy tomcat project. I have few questions :
1. The commons-modeler jar available at repos is
at 1.1M1. We currently use 1.1.
Should we change to 1.1M1?
No, please use
Jacek,
Thanks and one more question/comment :
The contents of var directory of tomcat go to
META-INF/geronimo/org.apache.geronimo/geronimo-tomcat/var
instead of META-INF/geronimo-tomcat/var in the jar.
Thanks
Anita
--- Jacek Laskowski [EMAIL PROTECTED] wrote:
2006/2/28, anita
I don't know either. I have begun looking at the console-web module migration.
Aaron, do I have your blessings to migrate that ? :-)
Cheers
Prasad
On 2/28/06, Jacek Laskowski [EMAIL PROTECTED] wrote:
2006/2/28, anita kulshreshtha [EMAIL PROTECTED]:
2. Is anyone writing the assembly-plugin?
2006/2/28, anita kulshreshtha [EMAIL PROTECTED]:
Jacek,
Thanks and one more question/comment :
The contents of var directory of tomcat go to
META-INF/geronimo/org.apache.geronimo/geronimo-tomcat/var
instead of META-INF/geronimo-tomcat/var in the jar.
I *guess* you're referring to the
--- Jacek Laskowski [EMAIL PROTECTED] wrote:
2006/2/28, anita kulshreshtha [EMAIL PROTECTED]:
Jacek,
Thanks and one more question/comment :
The contents of var directory of tomcat go to
META-INF/geronimo/org.apache.geronimo/geronimo-tomcat/var
instead of
I have attached the pom.xml to jira. The missing
tomcat poms have been added to the repo. We still have
to wait for commons-modeler-1.1.jar.
Thanks
Anita
--- anita kulshreshtha [EMAIL PROTECTED] wrote:
--- Jacek Laskowski [EMAIL PROTECTED] wrote:
2006/2/28, anita kulshreshtha
inline .
--- Alan D. Cabrera [EMAIL PROTECTED] wrote:
On 2/20/2006 3:20 AM, Gianny Damour wrote:
Alan D. Cabrera wrote:
Does the entire system need to build using a
single command for this
interim conversion? Why not have people do a
mvn install
maven new
The mvn
Anita,
Do you have the following in your POM ?
repositories
repository
snapshots
enabledtrue/enabled
/snapshots
idApache CVS/id
nameApache CVS of the Central Repository/name
urlhttp://cvs.apache.org/maven-snapshot-repository/url
/repository
2006/2/27, anita kulshreshtha [EMAIL PROTECTED]:
I am trying to build with mvn install! I get the
following error?
[INFO]
-
[ERROR] BUILD ERROR
[INFO]
2006/2/27, Prasad Kashyap [EMAIL PROTECTED]:
Anita,
Do you have the following in your POM ?
repositories
repository
snapshots
enabledtrue/enabled
/snapshots
idApache CVS/id
nameApache CVS of the Central Repository/name
2006/2/21, Prasad Kashyap [EMAIL PROTECTED]:
Sure.
I'll try to write a summary of the final strategy most of us agreed
upon. I don't know if that needs to be voted or something. But I'll
put it out there.
Well, it's always about a concensus so if we're about to fight I'm
sure the vote will
Jacek,
JIRAs are fine as long as they all stay bunched together (using a
special keyword, maybe). Thanx for opening them for us.
After having discussed very many designs, a detailed summary of the
final design that we all agreed on should be available someplace.
Either copy/pasted into each of
I would create one parent issue w/ many sub-tasks, one for each module.
Regards,
Alan
On 2/21/2006 7:42 AM, Prasad Kashyap wrote:
Jacek,
JIRAs are fine as long as they all stay bunched together (using a
special keyword, maybe). Thanx for opening them for us.
After having discussed very
2006/2/21, Alan D. Cabrera [EMAIL PROTECTED]:
I would create one parent issue w/ many sub-tasks, one for each module.
I would do it, too. That's exactly the aim of
https://issues.apache.org/jira/browse/GERONIMO-851, I thought.
Alan
Jacek
--
Jacek Laskowski
http://www.laskowski.org.pl
2006/2/21, Prasad Kashyap [EMAIL PROTECTED]:
Jacek,
JIRAs are fine as long as they all stay bunched together (using a
special keyword, maybe). Thanx for opening them for us.
I have opened a couple of subtasks of
https://issues.apache.org/jira/browse/GERONIMO-851 that I had known
was being
Sure.
I'll try to write a summary of the final strategy most of us agreed
upon. I don't know if that needs to be voted or something. But I'll
put it out there.
Cheers
Prasad
On 2/21/06, Jacek Laskowski [EMAIL PROTECTED] wrote:
2006/2/21, Prasad Kashyap [EMAIL PROTECTED]:
Jacek,
JIRAs are
Just throwing this out there:
The basic directory structure for maven2 is ${parent.artifactId}/$
{artifactId}. If we deviate from that we'll have to do crazy things
like put a precise scm url in each pom.xml.
This means two things:
1. there needs to be modules/pom.xml which is the
2006/2/20, Alan D. Cabrera [EMAIL PROTECTED]:
Does the entire system need to build using a single command for this
interim conversion? Why not have people do a
mvn install
maven new
The mvn install will build both maven 1 and 2 jars. The maven new
will use the maven 1 jars.
Very good
I would like to migrate tomcat and tomcat-builder
if it is not already taken?
Thanks
Anita
--- Jacek Laskowski [EMAIL PROTECTED] wrote:
2006/2/20, Gianny Damour
[EMAIL PROTECTED]:
I think that this has already been suggested by
David J.: we add a goal,
e.g. new000, which is
2006/2/20, anita kulshreshtha [EMAIL PROTECTED]:
I would like to migrate tomcat and tomcat-builder
if it is not already taken?
AFAIK, it is not. Go for it! Create a JIRA task item. Attach it to
http://issues.apache.org/jira/browse/GERONIMO-851 and go ahead.
Anita
Jacek
--
Jacek
We should have a wiki page with the modules list so that people can sign up ?
The page could also mark complete those modules already done.
I shall spare some cycles for it during this week as I wrap up my
itests subproject infrastructure. I shall devote full time towards
more modules conversion
2006/2/20, Prasad Kashyap [EMAIL PROTECTED]:
We should have a wiki page with the modules list so that people can sign up ?
Hi Prasad,
Wouldn't it be better off having a set of JIRA tasks and let people
pick their favorities? I'll create them.
I'm about to commit some changes wrt Maven2 support
2006/2/20, Jacek Laskowski [EMAIL PROTECTED]:
I'm about to commit some changes wrt Maven2 support that should help
people get started and jump in. I'm checking it out at the moment.
Done. The change is committed and ready to give it a try. It won't
possibly work on operating systems other than
On 2/20/2006 12:29 AM, Jacek Laskowski wrote:
2006/2/20, Alan D. Cabrera [EMAIL PROTECTED]:
Does the entire system need to build using a single command for this
interim conversion? Why not have people do a
mvn install
maven new
The "mvn install" will build both maven 1 and 2
On 2/20/2006 3:20 AM, Gianny Damour wrote:
Alan D. Cabrera wrote:
Does the entire system need to build using a single command for this
interim conversion? Why not have people do a
mvn install
maven new
The mvn install will build both maven 1 and 2 jars. The maven
new will use the maven
On 2/17/2006 1:35 AM, Anders Hessellund Jensen wrote:
Gianny Damour wrote:
Basically, this is how I see a migration module by module working:
1. take one module;
2. write its pom.xml;
3. remove from its project.xml all the external dependencies, i.e.
the non Geronimo dependencies (they are
Gianny Damour wrote:
Basically, this is how I see a migration module by module working:
1. take one module;
2. write its pom.xml;
3. remove from its project.xml all the external dependencies, i.e. the
non Geronimo dependencies (they are no more required as they are now
defined by pom.xml); and
2006/2/15, Anders Hessellund Jensen [EMAIL PROTECTED]:
Dain Sundstrom wrote:
What do you mean by in parallel?
I just mean that both the m1 and the m2 build runs, without interfering
with each other.
Exactly what I meant too! I wish we don't touch any m1-based files in
our build and add
Jacek Laskowski wrote:
As far as i know,it is not possible to use m2 dependencies in m1, so if
we want to do that we would have to write a m1 plugin for that ourselves.
It is. Just define layoutlegacy/layout as a type of a repository.
Cool. Is it possible to make m2 deploy the builds to the
2006/2/15, Anders Hessellund Jensen [EMAIL PROTECTED]:
Cool. Is it possible to make m2 deploy the builds to the local m1
repository as part of the build process? That would be very helpful.
I haven't tested it, but the specs' pom.xml uses such a plugin -
maven-one-plugin.
plugin
Jacek Laskowski wrote:
2006/2/15, Gianny Damour [EMAIL PROTECTED]:
Hi,
I also think that we should call m2 from m1 and avoid to maintain a dual
build during the migration. As pointed out by Dain, we could easily call
m2 from m1 by redefining the clean and build goals of m1 to invoke m2
Gianny Damour wrote:
Basically, this is how I see a migration module by module working:
1. take one module;
2. write its pom.xml;
3. remove from its project.xml all the external dependencies, i.e. the
non Geronimo dependencies (they are no more required as they are now
defined by pom.xml); and
Anders Hessellund Jensen wrote:
Gianny Damour wrote:
Basically, this is how I see a migration module by module working:
1. take one module;
2. write its pom.xml;
3. remove from its project.xml all the external dependencies, i.e.
the non Geronimo dependencies (they are no more required as
Gianny Damour wrote:
Basically, this is how I see a migration module by module working:
1. take one module;
2. write its pom.xml;
3. remove from its project.xml all the external dependencies, i.e. the
non Geronimo dependencies (they are no more required as they are now
defined by pom.xml); and
On Feb 15, 2006, at 4:49 AM, Jacek Laskowski wrote:
2006/2/15, Anders Hessellund Jensen [EMAIL PROTECTED]:
We need a m2 version of the geronimo-dependency-plugin. Is anyone
working on this, or perhaps it already exists somewhere?
AFAIK, the answers are no and no, appropriately. If you'd
That's right. I have the deployment plugin in m2. I'm testing each of
the goals one by one as I use them in the itests project. The itests
project is also in m2.
I like Gianny's roadmap. We'll know the potholes and pitfalls only
when we start driving. So either we could randomly take a few
Prasad Kashyap wrote:
That's right. I have the deployment plugin in m2. I'm testing each of
the goals one by one as I use them in the itests project. The itests
project is also in m2.
I like Gianny's roadmap. We'll know the potholes and pitfalls only
when we start driving. So either we could
On Feb 15, 2006, at 5:25 AM, Gianny Damour wrote:
Then I don't understand why it would save us any work *now*? How
could
m1 and m2 know about the dependencies if there were no project.xml or
pom.xml, respectively? Once we provide pom.xml's, I understand it
would be the next step to just call
On Feb 14, 2006, at 5:28 PM, Brett Porter wrote:
On 2/15/06, David Blevins [EMAIL PROTECTED] wrote:
Every m2 project i've worked with eventually ended up leveraging
maven 1 repositories.
We'd likely use the maven-one-plugin which puts jars into a maven 1
repo. Also we'd likely still need to
On Feb 15, 2006, at 11:29 AM, Anders Hessellund Jensen wrote:
geronimo-system has some jelly to create a geronimo-
version.properties file.
Check out how I create the openejb-version.properties via the maven-
antrun-plugin here:
David Blevins wrote, On 2/14/2006 5:29 PM:
On Feb 14, 2006, at 5:01 PM, Dain Sundstrom wrote:
On Feb 14, 2006, at 4:30 PM, David Blevins wrote:
On Feb 14, 2006, at 4:06 PM, Dain Sundstrom wrote:
Is there an easy way to do this with m1? I'm concerned about
having two dependency lists:
I'd like to help migrating to maven 2.
Where to start? I suppose a good start would be to write POM's for some
of the modules. This should be fairly straightforward, at least for
modules without complex jelly usage. Should the directory layout be
configured to maven 1 style in the parent POM
On 2/14/2006 3:09 AM, Anders Hessellund Jensen (Trifork) wrote:
I'd like to help migrating to maven 2.
Where to start? I suppose a good start would be to write POM's for
some of the modules. This should be fairly straightforward, at least
for modules without complex jelly usage. Should
:
I'd like to help migrating to maven 2.
Where to start? I suppose a good start would be to write POM's for
some of the modules. This should be fairly straightforward, at
least for modules without complex jelly usage. Should the
directory layout be configured to maven 1 style in the parent POM
migrating to maven 2.
Where to start? I suppose a good start would be to write POM's for
some of the modules. This should be fairly straightforward, at
least for modules without complex jelly usage. Should the
directory layout be configured to maven 1 style in the parent POM?
We've tried
2006/2/14, Dain Sundstrom [EMAIL PROTECTED]:
If m2 could exec an m1 build (following global dependencies) or if m1
could invoke m2, this conversion would be much easier as we could
convert a module at at time.
As far as I understood it, it's not possible. What is possible is to
build Maven2
On Feb 14, 2006, at 2:03 PM, Alan D. Cabrera wrote:
On 2/14/2006 3:09 AM, Anders Hessellund Jensen (Trifork) wrote:
I'd like to help migrating to maven 2.
Where to start? I suppose a good start would be to write POM's for
some of the modules. This should be fairly straightforward
:
I'd like to help migrating to maven 2.
Where to start? I suppose a good start would be to write POM's for
some of the modules. This should be fairly straightforward, at least
for modules without complex jelly usage. Should the directory layout
be configured to maven 1 style in the parent POM
I have submitted a patch migrating some of the simpler modules to Maven
2. The m2 build runs parallel with the m1 build. Nothing has been
touched except POM files.
http://issues.apache.org/jira/browse/GERONIMO-1624
I suggest we continue along that path, making the m2 build run parallel
with
I thought the biggest problem was that not all of our dependencies had
valid POMs, or at least not all their transitive dependencies had
valid POMs, so any Geronimo build eventually ran into missing/invalid
POMs and crapped out. There was a Wiki page where progress on this
front was being
2006/2/15, Aaron Mulder [EMAIL PROTECTED]:
I thought the biggest problem was that not all of our dependencies had
valid POMs, or at least not all their transitive dependencies had
valid POMs, so any Geronimo build eventually ran into missing/invalid
POMs and crapped out. There was a Wiki page
Aaron Mulder wrote:
I thought the biggest problem was that not all of our dependencies had
valid POMs, or at least not all their transitive dependencies had
valid POMs, so any Geronimo build eventually ran into missing/invalid
POMs and crapped out. There was a Wiki page where progress on this
What do you mean by in parallel?
I specifically would like to see modules converted one by one to m2
and when converted have the module completely built by m2 (execed?)
from a m1 global build. I think this is the only way we will ever
keep our m1 and m2 builds in sync during the
On Feb 14, 2006, at 4:06 PM, Dain Sundstrom wrote:
Is there an easy way to do this with m1? I'm concerned about
having two dependency lists: one in the project.xml and one in the
pom.xml. Is there a tool that can merge the project.xml
dependencies into a template pom.xml?
If there was
Dain Sundstrom wrote:
What do you mean by in parallel?
I just mean that both the m1 and the m2 build runs, without interfering
with each other.
I specifically would like to see modules converted one by one to m2 and
when converted have the module completely built by m2 (execed?) from a
David Blevins wrote:
Why don't we:
- use an non-conflicting groupId like org.apache.geronimo-m2 or
something specifically for conversion
- set it up in our continuum install as another project
- and continuously build *both*
?
The reason for the new groupId is so that the m2 build
On Feb 14, 2006, at 4:30 PM, David Blevins wrote:
On Feb 14, 2006, at 4:06 PM, Dain Sundstrom wrote:
Is there an easy way to do this with m1? I'm concerned about
having two dependency lists: one in the project.xml and one in the
pom.xml. Is there a tool that can merge the project.xml
On Feb 14, 2006, at 4:48 PM, Anders Hessellund Jensen wrote:
David Blevins wrote:
Why don't we:
- use an non-conflicting groupId like org.apache.geronimo-m2 or
something specifically for conversion
- set it up in our continuum install as another project
- and continuously build
On 2/15/06, David Blevins [EMAIL PROTECTED] wrote:
Every m2 project i've worked with eventually ended up leveraging
maven 1 repositories.
We'd likely use the maven-one-plugin which puts jars into a maven 1
repo. Also we'd likely still need to list cvs.apache.org in the repo
list of our m2
On Feb 14, 2006, at 5:01 PM, Dain Sundstrom wrote:
On Feb 14, 2006, at 4:30 PM, David Blevins wrote:
On Feb 14, 2006, at 4:06 PM, Dain Sundstrom wrote:
Is there an easy way to do this with m1? I'm concerned about
having two dependency lists: one in the project.xml and one in
the
Please, no -m2 suffix.
--jason
On 2/14/06, David Blevins [EMAIL PROTECTED] wrote:
On Feb 14, 2006, at 4:06 PM, Dain Sundstrom wrote:
Is there an easy way to do this with m1? I'm concerned about
having two dependency lists: one in the project.xml and one in the
pom.xml. Is there a
86 matches
Mail list logo
