2009/5/15 Christian Schulte
> Joerg Hohwiller schrieb:
> > Why? In SCM there should never be a non-snapshot module with snapshot
> > dependencies. Further a non-snapshot module should not be modified except
> > for pom.xml
>
> /trunk at revision 4
> +root(1.2-SNAPSHOT)
> +A(1.0)
> +B(1.3-SNAPSH
On May 14, 2009, at 9:18 PM, Christian Schulte wrote:
Why? In SCM there should never be a non-snapshot module with snapshot
dependencies. Further a non-snapshot module should not be modified
except
for pom.xml
/trunk at revision 4
+root(1.2-SNAPSHOT)
+A(1.0)
+B(1.3-SNAPSHOT)
If the pom
Joerg Hohwiller schrieb:
> Hi Christian,
>
>> My question may have sounded rhetorically but I really meant that. You
>> could of course manage commit rights with subversion so that whenever
>> someone mistakenly would try to commit to that release version on trunk,
>> subversion could simply disal
Can we move this out of here and do in some other part of the
configuration processing? I would like to try and remove this
signature from Plexus for 1.0, it was added specifically for Maven and
I think we can process it when we process the configuration elsewhere.
On 14-May-09, at 5:02 PM,
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
> Ask someone why you have to invoke eclipse:eclipse on toplevel everytime.
> If the dependency of some-module has changed, you can NOT invoke
> eclipse:eclipse
> just on some-module since the plugin then wants to resolve the dependencies
> from the repository and adds JAR-Dependencies to the IDE
>
>
> OK. So you would NOT mind if maven adds some new features that
> are compatible to older versions of maven.
> Thats all I am fighting for.
>
No fighting required, just make a patch. If it's truly backwards compatible,
then there wouldn't be much reason for it to be declined.
I'm interested
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Christian,
>
> My question may have sounded rhetorically but I really meant that. You
> could of course manage commit rights with subversion so that whenever
> someone mistakenly would try to commit to that release version on trunk,
> subversion c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Chistian,
>
> What stops a developer from making changes to A(1.0) on trunk,
> rebuilding locally - that is - overwriting release artifacts with
> something different in the local repository, and then later on even
> commit those changes forgettin
Ok, the vote for the ant-tasks is cancelled. I will add some configuration to
the pom of the ant tasks to generate the source zip, and restart the process.
Benjamin Bentmann wrote:
Paul Gier wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-018/
I think
Paul Gier wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-018/
I think for the same reason Brian pointed out for Doxia (violation of
ASF policy due to missing source bundle), we have to cancel this release
and either wait for the updated parent or extend
Hi Brian,
That would be fantastic!
Cheers,
Daniel
Brian Fox a écrit :
> We can try a release maybe next week. We first have to get some assembly and
> parent pom things fixed to get our releases back in compliance with asf
> policy.
>
> On Thu, May 14, 2009 at 8:42 AM, Nick Stolwijk wr
It's on my todo list.
michael.hinterse...@spx.com wrote:
>
> Hi developers
>
> I was wondering if there is a schedule for the maven-ejb-plugin 2.2
> release?
> All issues are closed since month, none has been created and our project
> is waiting for an official release to solve one of the issues
I was blocked by some IT issues in the assembly plugin. I broke through that
last night, so I can finish up the ITs. David Jenks found another issue with
2.2-beta-3 that causes the source jars to be packaged with absolute paths. I
will need to fix this as well before we can use it globally. If you
We can try a release maybe next week. We first have to get some assembly and
parent pom things fixed to get our releases back in compliance with asf
policy.
On Thu, May 14, 2009 at 8:42 AM, Nick Stolwijk wrote:
> I don't know when it will be released, but take a look at [1] for how
> to workaroun
On Thu, May 14, 2009 at 3:10 PM, Lukas Theussl wrote:
>
> After some discussion on irc it seems we don't have a mechanism in place
> yet for a straightforward release process that also complies with current
> Apache policies.
Yep. Can we have a status please? Can we help? I am waiting for this
After some discussion on irc it seems we don't have a mechanism in place yet for a
straightforward release process that also complies with current Apache policies.
This vote is cancelled, I will start another attempt as soon as there is some
consensus on the actual requirements, and a well-de
I don't know when it will be released, but take a look at [1] for how
to workaround haveing SNAPSHOT dependencies.
[1]
http://www.sonatype.com/people/2009/01/best-practices-for-releasing-with-3rd-party-snapshot-dependencies/
Hth,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
20
There's no source bundle.
On Thu, May 14, 2009 at 3:59 AM, Lukas Theussl wrote:
>
> Hi,
>
> We solved 27 (Doxia) and 3 (Sitetools) issues:
>
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780&styleName=Html&version=15073
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?proj
+1
2009/5/14 Olivier Lamy
> +1
> --
> Olivier
>
> 2009/5/14 Vincent Siveton :
> > +1
> >
> > Vincent
> >
> > 2009/5/14 Lukas Theussl :
> >>
> >> Hi,
> >>
> >> We solved 27 (Doxia) and 3 (Sitetools) issues:
> >>
> >>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780&styleName=Htm
+1
--
Olivier
2009/5/14 Vincent Siveton :
> +1
>
> Vincent
>
> 2009/5/14 Lukas Theussl :
>>
>> Hi,
>>
>> We solved 27 (Doxia) and 3 (Sitetools) issues:
>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780&styleName=Html&version=15073
>> http://jira.codehaus.org/secure/ReleaseNote
+1
- Fabrice
belling...@apache.org
On Thu, May 14, 2009 at 9:59 AM, Lukas Theussl wrote:
>
> Hi,
>
> We solved 27 (Doxia) and 3 (Sitetools) issues:
>
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780&styleName=Html&version=15073
>
> http://jira.codehaus.org/secure/ReleaseNo
+1
Vincent
2009/5/14 Lukas Theussl :
>
> Hi,
>
> We solved 27 (Doxia) and 3 (Sitetools) issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780&styleName=Html&version=15073
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11624&styleName=Html&version=15075
>
> The
Dear all,
Does anybody have an idea of the ETA of maven-compiler-plugin 2.1 release?
I do rely on 2.1-SNAPSHOT for my builds, so I cannot use maven release
process currently.
I am about to release SAT4J 2.1 in a few weeks, I would have liked to
embrace fully maven for that.
Cheers,
Hi,
We solved 27 (Doxia) and 3 (Sitetools) issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780&styleName=Html&version=15073
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11624&styleName=Html&version=15075
There are still a couple of issues left in JIRA:
http:
25 matches
Mail list logo
