2010/4/30 Ramiro Pereira de Magalhães :
> Hey there people!
>
> I work for a company that uses Eclipse and Maven a lot, therefore, I use a
> lot the maven-eclipse-plugin. I'm starting to need some improvements made and
> fixes done for this plugin, therefor I joined this mailing list to try to
>
Issue Subscription
Filter: Design & Best Practices (22 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
Hey there people!
I work for a company that uses Eclipse and Maven a lot, therefore, I use a lot
the maven-eclipse-plugin. I'm starting to need some improvements made and fixes
done for this plugin, therefor I joined this mailing list to try to help you
guys improve it. I hope I can help someho
Henrique Prange wrote:
I've tried to build a project with multiple modules using Maven
3.0-beta-1 unsuccessfully. I got some weird compilation problems
"weird compilation problems" belong to those kind of problems that are
nearly impossible to troubleshoot. Concrete solutions require concrete
Hi all,
I've tried to build a project with multiple modules using Maven
3.0-beta-1 unsuccessfully. I got some weird compilation problems on
child modules when trying to build from the parent module. But if I try
to build the child module directly, it works.
Any thoughts if is it a bug or som
On 29/04/2010, at 10:50 PM, sebb wrote:
> On 29/04/2010, Brett Porter wrote:
>> The correct one for reporting problems (vs new uploads) is:
>> http://jira.codehaus.org/browse/MEV
>>
>> In general, you want to make sure it is fixed at the source first if it's an
>> imported forge like Apache's
On 29/04/2010, Brett Porter wrote:
> The correct one for reporting problems (vs new uploads) is:
> http://jira.codehaus.org/browse/MEV
>
> In general, you want to make sure it is fixed at the source first if it's an
> imported forge like Apache's.
So, is the correct procedure as follows:
1) U
The correct one for reporting problems (vs new uploads) is:
http://jira.codehaus.org/browse/MEV
In general, you want to make sure it is fixed at the source first if it's an
imported forge like Apache's.
- Brett
On 29/04/2010, at 9:45 PM, Juven Xu wrote:
> I think people can create tasks here:
I think people can create tasks here:
http://jira.codehaus.org/browse/MAVENUPLOAD
or at Sonatype:
https://issues.sonatype.org/browse/OSSRH
On Thu, Apr 29, 2010 at 4:12 PM, sebb wrote:
> OK thanks very much.
>
> If this problem recurs with other projects, is there a formal means of
> reporting i
OK thanks very much.
If this problem recurs with other projects, is there a formal means of
reporting it?
e.g. via an issue tracker?
On 29/04/2010, Juven Xu wrote:
> checksums on pgp signautes are deleted.
>
>
> On Wed, Apr 28, 2010 at 11:34 PM, sebb wrote:
>
> > On 28/04/2010, Juven Xu wrot
10 matches
Mail list logo