On 06/10/05, Brett Porter [EMAIL PROTECTED] wrote:
As Joerg mentions, the artifact plugin (1.5.2 for Maven 1.0.2, or 1.6
as included in Maven 1.1 beta 2) now deploys a complete pom instead. I
have closed MAVEN-1390 as won't fix.
Okay thanks, I just wanted to make sure this was the right way
On 06/10/05, Mark Hobson [EMAIL PROTECTED] wrote:
On 06/10/05, Brett Porter [EMAIL PROTECTED] wrote:
As Joerg mentions, the artifact plugin (1.5.2 for Maven 1.0.2, or 1.6
as included in Maven 1.1 beta 2) now deploys a complete pom instead. I
have closed MAVEN-1390 as won't fix.
Okay
On 10/6/05, Mark Hobson [EMAIL PROTECTED] wrote:
These look like they'll repoclean okay to me - can anyone see any
probs before I confirm?
They look good to me.
- Brett
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
On 06/10/05, Brett Porter [EMAIL PROTECTED] wrote:
They look good to me.
Thanks, they should be in the next release.
Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
I'm trying to resolve MEV-3 which led to this discussion:
http://thread.gmane.org/gmane.comp.java.picocontainer.user/723
It appears that multiproject m1 poms and project.properties are the
core problems - MAVEN-1390 and friends. What is the official maven
stance regarding these features
As Joerg mentions, the artifact plugin (1.5.2 for Maven 1.0.2, or 1.6
as included in Maven 1.1 beta 2) now deploys a complete pom instead. I
have closed MAVEN-1390 as won't fix.
- Brett
On 10/5/05, Mark Hobson [EMAIL PROTECTED] wrote:
Hi,
I'm trying to resolve MEV-3 which led to this
