-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Brian,
Are you using the release plugin?
Nope! I tried it and came to the point that is no good for me.
I also had a discussion with the developers long time ago
and filed some feature request. Anyhow I still think this
is the wrong approach
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Milos,
relying on the reactor and giving up on being able to build the one project
separately is very bad (read: completely breaks) any IDE integration.
I totally disagree. I am successfully using maven-eclipse-plugin (mvn
eclipse:eclipse) and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Ralph,
Hi there,
absolutely everybody having large maven projects is
annoyed by maintaining the versions in all the poms.
Are you using the release plugin?
This problem probably goes away for anyone able to use the release
plugin, but
Can you give more details about what doesn't work or doesn't match your
process?
E.g. it tried to convince me to release all modules of my entire project
and complained if some module had a non SNAPSHOT version.
Since it's going to convert a module to a release version, you shouldn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian Fox wrote:
Can you give more details about what doesn't work or doesn't match your
process?
E.g. it tried to convince me to release all modules of my entire project
and complained if some module had a non SNAPSHOT version.
Since it's
As I already said, I talked about release-plugin and my view of the world
and it seems NOT to fit together. My POM-tree follows strict logical
aspects that is motivated by the architecture of the project and NOT by
the philosophy of some plugin.
I'm trying to understand your structure and
On May 12, 2009, at 5:43 PM, Brian Fox wrote:
My POM-tree follows strict logical aspects that is motivated by the
architecture of the project and NOT by the philosophy of some plugin.
You do know these folks are trying to help, right? ;)
Christian.
Christian Edward Gruber
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi again,
I did not yet get the point, why you have to write a new pom.xml to the disc.
My naive illusion was that there is a central component that reads and parses
the POM in maven where you can hook into and perform the transformation.
Then
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Brian,
As I already said, I talked about release-plugin and my view of the world
and it seems NOT to fit together. My POM-tree follows strict logical
aspects that is motivated by the architecture of the project and NOT by
the philosophy of
On May 12, 2009, at 2:43 PM, Brian Fox wrote:
As I already said, I talked about release-plugin and my view of the
world
and it seems NOT to fit together. My POM-tree follows strict logical
aspects that is motivated by the architecture of the project and
NOT by
the philosophy of some
On May 12, 2009, at 3:01 PM, Joerg Hohwiller wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi again,
I did not yet get the point, why you have to write a new pom.xml to
the disc.
My naive illusion was that there is a central component that reads
and parses
the POM in maven where
On May 12, 2009, at 3:43 PM, Ralph Goers wrote:
On May 12, 2009, at 2:43 PM, Brian Fox wrote:
As I already said, I talked about release-plugin and my view of
the world
and it seems NOT to fit together. My POM-tree follows strict logical
aspects that is motivated by the architecture of
Ralph Goers schrieb:
On May 12, 2009, at 2:43 PM, Brian Fox wrote:
As I already said, I talked about release-plugin and my view of the
world
and it seems NOT to fit together. My POM-tree follows strict logical
aspects that is motivated by the architecture of the project and
NOT by
On May 12, 2009, at 6:20 PM, David Jencks wrote:
On May 12, 2009, at 3:43 PM, Ralph Goers wrote:
On May 12, 2009, at 2:43 PM, Brian Fox wrote:
As I already said, I talked about release-plugin and my view of
the world
and it seems NOT to fit together. My POM-tree follows strict
On May 12, 2009, at 6:17 PM, Christian Schulte wrote:
Ralph Goers schrieb:
On May 12, 2009, at 2:43 PM, Brian Fox wrote:
As I already said, I talked about release-plugin and my view of the
world
and it seems NOT to fit together. My POM-tree follows strict
logical
aspects that is
Hi,
We solved 13 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11533styleName=Htmlversion=14199
There are still several issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11533status=1
Staging repo:
Hi,
Just a quick note to say thanks for the advice and tips this list has
provided so far in helping me extend the maven-clover2-plugin to now
support Test Optimization of Integration/Functional Tests.
If your current project has problems with your unit or functional
tests taking too
Ralph Goers schrieb:
Imagine that you could get a pom.xml for all of Apache Commons that
contained the dependency management for it. Every time a commons
project released a new Commons bill of materials would go with it.
a) You want all the projects to be part of the build to be sure
On May 12, 2009, at 9:30 PM, Christian Schulte wrote:
Ralph Goers schrieb:
Imagine that you could get a pom.xml for all of Apache Commons that
contained the dependency management for it. Every time a commons
project released a new Commons bill of materials would go with it.
a) You want all
It sounds like some people should have a look at the
versions-maven-plugin...
ok, so it will still force updating your pom, but it will allow releasing
individual modules using the release plugin and then updating the reactor to
reflect the new release.
-Stephen
20 matches
Mail list logo
