release plugin issue

["DeGrande, Rick" <Ri...@firstdata.com>]

I've configured the release plugin in my build.  I'm using a flat
directory structure like:

 

Aggregator

Common

Ejb

Web

 

When I do a release:prepare from the aggregator directory everything
seems to work however the aggregator/... is the only path labeled.

 

Also, when I do a release:perform from the aggregator directory it fails
looking for the sibling directories in the aggregator/target/sibling.
Maven identifies aggregator/target/checkout as the working directory.
Is this because of the directory structure I'm using ?  Does the
release-plugin only work with a hierarchical dir?  Is there a way around
this or do I need to change the dir structure I'm using ?

 

Thanks

 




-----------------------------------------
The information in this message may be proprietary and/or
confidential, and protected from disclosure.  If the reader of this
message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify First Data
immediately by replying to this message and deleting it from your
computer. 

Re: release plugin issue

[Marshall Schor <ms...@schor.com>]

 I'm also using a flat structure.

I found that the keys to making this work seem to be:

1) use release 2.0 of the release plugin.  This is the release with the support
for "flat" hierarchies.  Note that the Apache common parent POM version 7 (the
latest) still doesn't specify this release, it specifies an earlier one
(2.0-beta-9) which doesn't have this support, so you have to override that - if
you're using the Apache common parent pom (i.e.
http://repo1.maven.org/maven2/org/apache/apache/7/apache-7.pom ).

2) in each pom in the flat hierarchy, insure the <scm> element is pointing to
the right place in your SVN or whatever.  If you let these "inherit" from parent
poms, the inheritance makes often wrong assumptions that the children of the
parent are located underneath the parent pom directory.  Specifying the actual
location overrides this behavior.

-Marshall Schor

On 7/9/2010 11:28 AM, DeGrande, Rick wrote:
> I've configured the release plugin in my build.  I'm using a flat
> directory structure like:
>
>  
>
> Aggregator
>
> Common
>
> Ejb
>
> Web
>
>  
>
> When I do a release:prepare from the aggregator directory everything
> seems to work however the aggregator/... is the only path labeled.
>
>  
>
> Also, when I do a release:perform from the aggregator directory it fails
> looking for the sibling directories in the aggregator/target/sibling.
> Maven identifies aggregator/target/checkout as the working directory.
> Is this because of the directory structure I'm using ?  Does the
> release-plugin only work with a hierarchical dir?  Is there a way around
> this or do I need to change the dir structure I'm using ?
>
>  
>
> Thanks
>
>  
>
>
>
>
> -----------------------------------------
> The information in this message may be proprietary and/or
> confidential, and protected from disclosure.  If the reader of this
> message is not the intended recipient, or an employee or agent
> responsible for delivering this message to the intended recipient,
> you are hereby notified that any dissemination, distribution or
> copying of this communication is strictly prohibited. If you have
> received this communication in error, please notify First Data
> immediately by replying to this message and deleting it from your
> computer. 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org