Issue Subscription
Filter: Design & Best Practices (24 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
Great,
FYI: with just a few simple adjustments QDox can be upgraded.
I'll provide a patch when the final 2.0 is released.
-Robert
> From: ol...@apache.org
> Date: Fri, 8 Apr 2011 22:07:47 +0200
> Subject: Re: Maven plugin tools + QDox
> To: dev@maven.apache.org
>
> no problem for me.
> mos
Ah, sorry, missed that attachment. I guess I'm still getting used to the
layout.
I'll look into it for the 2.3 release.
On 4/14/11 2:26 PM, sebb wrote:
On 14 April 2011 16:47, John Casey wrote:
On 4/14/11 11:37 AM, sebb wrote:
On 14 April 2011 15:26, John Caseywrote:
mvn package in
On 14 April 2011 16:47, John Casey wrote:
>
>
> On 4/14/11 11:37 AM, sebb wrote:
>>
>> On 14 April 2011 15:26, John Casey wrote:
>>>
>>> mvn package install == mvn install
>>
>> Except that it behaves differently, which is why I think it may be
>> something more than just an assembly bug ...
>>
>
+1
--
Olivier
2011/4/13 Stephen Connolly :
> Hi,
>
> This release is being requested to assist the Apache Cassandra project.
>
> We solved 1 issue:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11533&styleName=Html&version=17307
>
> There are still a plenty of issues left in JIRA:
On 4/14/11 11:37 AM, sebb wrote:
On 14 April 2011 15:26, John Casey wrote:
mvn package install == mvn install
Except that it behaves differently, which is why I think it may be
something more than just an assembly bug ...
Are you talking about assemblies created by previous Maven executio
On 14 April 2011 15:26, John Casey wrote:
> mvn package install == mvn install
Except that it behaves differently, which is why I think it may be
something more than just an assembly bug ...
> Are you talking about assemblies created by previous Maven executions, that
> are just lying around in
mvn package install == mvn install
Are you talking about assemblies created by previous Maven executions,
that are just lying around in file form in the target/ directory?
Is there a project out there I can take a look at that will exhibit the
problem?
On 4/14/11 9:20 AM, sebb wrote:
The a
The assembly plugin is broken for versions after 2.2-beta-5.
Both 2.2 and 2.2.1 ignore attached assemblies which are defined in the
parent pom when running "mvn install".
However the attached assemblies are processed if one runs "mvn clean
install" or "mvn package install", and they are also proc
I've redeployed the site with your fix applied. Seems to be OK, but
you'd need to use the proxies or await the sync
On 13 April 2011 20:21, Lukas Theussl wrote:
>
> I committed it: http://svn.apache.org/viewvc?view=revision&revision=1091756
>
> -Lukas
>
>
> Stephen Connolly wrote:
>>
>> care to s
+1
-Lukas
Stephen Connolly wrote:
Hi,
This release is being requested to assist the Apache Cassandra project.
We solved 1 issue:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11533&styleName=Html&version=17307
There are still a plenty of issues left in JIRA:
http://jira.codeha
11 matches
Mail list logo
