Issue Subscription
Filter: Design & Best Practices (28 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
+1
--
Olivier
2009/10/30 Benjamin Bentmann :
> Hi,
>
> if some of you have a déjà vu while regarding the mail title, that's fine...
> my previous attempt at making our release processes smoother failed due to
> missing site descriptors in the deployment. So if you liked the predecessor
> versions
+1 from me
-Stephen
2009/10/29 Benjamin Bentmann
> Hi,
>
> if some of you have a déjà vu while regarding the mail title, that's
> fine... my previous attempt at making our release processes smoother failed
> due to missing site descriptors in the deployment. So if you liked the
> predecessor ve
Hi,
if some of you have a déjà vu while regarding the mail title, that's
fine... my previous attempt at making our release processes smoother
failed due to missing site descriptors in the deployment. So if you
liked the predecessor versions of the parents being voted on, I hope you
also like
Hi,
Firstly, this is great news :) See my comments below:
> 1. What releases are needed?
>
> maven-doxia-tools-1.1
> doxia-1.1.2
> doxia-sitetools-1.1.2
> maven-site-plugin-2.1
I guess yes, lukas?
> 2. Which issues do we include?
>
> Here's a list of the issues currently scheduled for the above
Also you'll want to wait until after Benjamin has released
maven-plugins:16 with the fixed site descriptors (or else release off
of maven-plugins:14 with the checkstyle overrides or you will be
unable to roll the project site)
-Stephen
2009/10/29 Vincent Siveton :
> Hi Dennis,
>
> For the changes
Hi Dennis,
For the changes plugin, we probably need to release before
maven-reporting-impl due to MSHARED-120
I could help you probably next week.
Cheers,
Vincent
2009/10/28 Dennis Lundberg :
> Hi
>
> I plan on making 2 releases in the near future:
>
> Maven Changes Plugin 2.2
> http://jira.cod
It's amazing how google's thread compression of a discussion can cause
me to overlook a huge thread so near and dear to my heart.
To start, Benjamin has hit the nail on the head of a discussion point
Jason and I have had going for quite some time. In fact, we even wrote
up a proposal for it months
Hi,
This is the first official release.
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=12063&resolution=-1&sorter/field=updated&sorter/order=DESC
Staging repo:
https://repository.apache.org/content/repositories/maven-
CANCELLED due to issues with org.apache.maven.plugins:maven-plugins:15
2009/10/29 Stephen Connolly
> Hi,
>
> This is the first official release.
>
> There are still a couple of issues left in JIRA:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=12063&resolution=
To be precise, the site descriptors are completely missing from central
for the three parents I released, i.e.:
- maven-parent:14
- maven-plugins:15
- maven-shared-components:13
effectively making those parents useless.
I was thinking about just adding those files (which are both tagged and
i
Hi,
This is the first official release.
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=12063&resolution=-1&sorter/field=updated&sorter/order=DESC
Staging repo:
https://repository.apache.org/content/repositories/maven-
Benjamin is on the case
This is just an FYI
-Stephen
+1
On Sun, Oct 25, 2009 at 11:18 AM, Benjamin Bentmann
wrote:
> Hi,
>
> This is a maintenance release for the assembly descriptor that we use to
> create ASF-compliant source distros. This release fixes a bug in version 1.0
> that erroneously includes paths like "target/**/src/**" in the distro.
+1
On Sun, Oct 25, 2009 at 11:25 AM, Benjamin Bentmann
wrote:
> Hi,
>
> these releases are primarily meant to incorporate the fixed source release
> assembly descriptor into our projects, thereby addressing the issue outlined
> in http://jira.codehaus.org/browse/MASSEMBLY-446.
>
> Furthermore, ma
The build use the plugin buildnumber-maven-plugin (which use native
svn with cli)
In order to get the svn rev when you use : mvn -v.
--
Olivier
2009/10/29 Henri Gomez :
>> If you have a missing SVN command, that may mean you do not have an
>> SVN client installed. You should have one installed on
2009/10/29 Henri Gomez :
>> If you have a missing SVN command, that may mean you do not have an
>> SVN client installed. You should have one installed on your path so
>> when you type "svn --version" (that's two dashes), you'll know what
>> version you have.
>
> yep, I know that, svn command is ins
> If you have a missing SVN command, that may mean you do not have an
> SVN client installed. You should have one installed on your path so
> when you type "svn --version" (that's two dashes), you'll know what
> version you have.
yep, I know that, svn command is installed on my OS/X but not on my
The Maven team is pleased to announce the release of Apache
Source-Release Assembly Descriptor, version 1.0.1.
This is a standardized assembly descriptor for use in the
maven-assembly-plugin. Source-release artifacts are archives which
contain the full project structure (sources only, no build ou
If you have a missing SVN command, that may mean you do not have an
SVN client installed. You should have one installed on your path so
when you type "svn --version" (that's two dashes), you'll know what
version you have.
Download a binary here:
http://subversion.tigris.org/
Paul
On Thu, Oct 29,
Hi to all,
After build Maven 3 from trunk
(https://svn.apache.org/repos/asf/maven/maven-3/trunk/) with ant, I
tried to build it with maven 2.2.1 but the build failed about a
missing svn command.
-
To unsubscribe, e-mail: dev-unsu
21 matches
Mail list logo
