On 02/10/2009, at 12:59 AM, Mark Hobson wrote:
2009/10/1 Brett Porter <[email protected]>:
On 30/09/2009, at 10:48 PM, Mark Hobson wrote:
These are released dependencies. They need to be SCM checkouts and
not source artifacts since they need to be buildable, i.e. contain
the
POM and any other necessary build resources.
You can build and release source bundles with all of that too :)
Interesting idea, have you got an example of this?
Every Maven project released in the last couple of months does this,
or the source bundle of Maven itself.
I'll investigate these points in more depth once I need to do the
work. I was mainly trying to gather whether it was appropriate to
add
this functionality to the assembly plugin. How did you see the POM
and SCM plugins coming into play here?
They were for doing the checkouts into a space the assembly plugin
could
pick it up and for modifying the <modules> element to include them
in a
build. You could put them in by hand in a profile though that is just
enabled by your scripts.
I hope to use mvn -r to avoid having to produce an aggregate pom that
contains the necessary <module> elements. Not sure how easy it'll be
to coax the SCM plugin into checking out all direct and transitive
dependencies of a project though.
Note that -r is deprecated in favour of -pl now...
Though if they are releases, I'd find going with source bundles
from the
repository easier than using the SCM.
I do like this idea, although it'd mean releasing new versions of
pre-existing projects to bring in the new attached artifact.
couldn't you build the equivalent source bundle for the existing
version, since it is a whole new artifact?
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
