Yeah,
I guess I feel the same and that's why I wanted to consult the dev list
first before raising a JIRA.
2016-05-03 23:21 GMT+02:00 Jörg Schaible :
> Hi Petar,
>
> Petar Tahchiev wrote:
>
> > Hi all,
> >
> > @Uwe - the enforcer rules are great, but I don't think I need them.
> > @Jorg - Resolv
Hi,
I just invited you as a member. So you can merge your pr.
Not sure how it works to cut release. You probably need some karma setup in
sonatype oss.
If it's a pain let me know and I will do it for you.
Olivier
On 4 May 2016 at 09:54, Christian Schulte wrote:
> Hi,
>
> is [https://github.com/
Hi,
is [https://github.com/codehaus-plexus/plexus-utils] the correct
repository to open pull requests at? I would like to merge a pull
request and create a 'plexus-utils-3.0.23' release. How is that done?
Which issue tracker to use? Whome/where to ask? etc.
Regards,
--
Christian
---
Hi Petar,
Petar Tahchiev wrote:
> Hi all,
>
> @Uwe - the enforcer rules are great, but I don't think I need them.
> @Jorg - Resolving the parent during release:prepare is fine. What I don't
> like is that it also asks me to resolve the platform version.
The point is, that Maven does not recreat
Hi Christian,
...i was already working on fix...but you have been faster...
Thanks for fixing it...
Kind regards
Karl Heinz
On 5/3/16 7:59 PM, schu...@apache.org wrote:
Repository: maven
Updated Branches:
refs/heads/master 5bac0a843 -> 70e2afd45
[MNG-6014] Removing ArtifactHandler for ejb3
Hi,
here is my +1.
Kind regards
Karl Heinz Marbaise
On 5/3/16 1:50 AM, Hervé BOUTEMY wrote:
Hi,
In preparation to Apache parent pom version 18, we need a little bugfix on
Apache Source Release Assembly Descriptor to fix MPOM-106
We solved 1 issue:
https://issues.apache.org/jira/secure/Release
Le mardi 3 mai 2016 09:55:31 Michael Osipov a écrit :
> > Hi,
> >
> > In preparation to Apache parent pom version 18, we need a little bugfix on
> > Apache Source Release Assembly Descriptor to fix MPOM-106
> >
> > We solved 1 issue:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proj
Hi all,
@Uwe - the enforcer rules are great, but I don't think I need them.
@Jorg - Resolving the parent during release:prepare is fine. What I don't
like is that it also asks me to resolve the platform version.
I'll go with Robert's suggestion.
2016-05-03 19:51 GMT+03:00 Jörg Schaible :
> Peta
Github user aqueance commented on the pull request:
https://github.com/apache/maven/pull/69#issuecomment-216595519
In addition to the problems mentioned above, that
[hack](https://github.com/apache/maven/blame/3533599e42a4a563abca33a69ed0f34c19815479/maven-aether-provider/src/main/java
Petar Tahchiev wrote:
> Hi guys,
>
> I have a question regarding the release plugin. In my project I have a BOM
> in which I declare a property and a dependencyManagement section:
>
> com.mycompany
> my-bom
> 1.0-SNAPSHOT
>
>
> 1.0-SNAPSHOT
>
>
>
>
> com.mycompany
> plat
Hi Petar,
I found a very old enforcer rule at smartics and asked them to provide
these as OS.
They did it two weeks ago at github under Apache Software License. :-)
Take a look at https://github.com/smartics/smartics-enforcer-rules
-- barthel
On May 3, 2016 4:25:55 PM Petar Tahchiev wrote
Hi Robert,
thank you for your comment. The idea behind the property was that I also
give the BOM to my clients and they declare it as their parent. So now if
they want to use a newer version of the platform, all they have to do
is redeclare the property to be 1.2 or 1.5 or whatever
they want. Oth
GitHub user jhaber opened a pull request:
https://github.com/apache/maven-shared/pull/10
Advance the index for longs and doubles
As you can see in the [stack overflow
answer](http://stackoverflow.com/questions/32255023/how-would-i-go-about-parsing-the-java-class-file-constant-pool/3
Why bother with the custom property? Do this instead and the release plugin is
happy:
com.mycompany
my-bom
1.0-SNAPSHOT
com.mycompany
platform
${project.version}
-Original Message-
From: Petar Tahchiev [mailto:paranoia...@gmail.com]
Sent: Tuesday, May 03,
Hi guys,
I have a question regarding the release plugin. In my project I have a BOM
in which I declare a property and a dependencyManagement section:
com.mycompany
my-bom
1.0-SNAPSHOT
1.0-SNAPSHOT
com.mycompany
platform
${platform.version}
and I also have 3 di
What you are describing is basically using "continuous" SNAPSHOT
dependencies.
Semantic Versioning is important for understanding API changes (and to
prevent such changes when not necessary). This could of course be computed
automatically, but there are also non-interface changes that a human need
> Hi,
>
> In preparation to Apache parent pom version 18, we need a little bugfix on
> Apache Source Release Assembly Descriptor to fix MPOM-106
>
> We solved 1 issue:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314621&version=12329542&styleName=Text
>
> Staging repo:
17 matches
Mail list logo
