Hello,
I know its not your problem domain, but I wanted to point out that the
OSGi bnd-tool can do exactly that. It can even differentiate for
interface providers and consumers.
http://www.aqute.biz/Bnd/Versioning
However the question is, if it really works all automatic if you are
not strictly
Looks like takari plugin test harness can't talk to one of your
project's repositories. Can you please open issue at github so we don't
spam this mailing list?
--
Regards,
Igor
On 2015-02-21 19:44, Cristiano Gavião wrote:
Hi again,
In order to investigate a bit more this strange behavior, I do
Thanks I'll check it out.
Mandy
On 2/19/2015 12:10 PM, Robert Scholte wrote:
Hi Mandy,
based on your proposal I've added 2 parameters:
dependenciesToAnalyzeIncludes and dependenciesToAnalyzeExcludes
This way it's not an All-Or-Nothing option, but instead you have full
control over the depende
Hi,I wrote 2 new enforces rules, the ability to specify a set of
mutually-exclusive profiles (p1,p2:p1,p3 would mean p1 can't be active with
either p2 pr p3) and the ability to ban profiles (the contrary of
requireActiveProfile). Both of these support wildcards.
I'd like to contribute these rule
Hi again,
In order to investigate a bit more this strange behavior, I downloaded
the apache-maven archive by hand (from
http://search.maven.org/#artifactdetails|org.apache.maven|apache-maven|3.2.3|pom).
Note that this is not the version that I have currently installed in my
linux. I'm using
Hi Igor,
That is strange...
I deleted all versions of apache-maven from local my repo.
Then I built (package) the takari-lifecycle (without testing) and no
version of apache-maven was downloaded.
But when I tried mvn install, the version 3.2.3 was downloaded but it
has only 178 bytes.
Don
With the repair to the hanging tests for Maven 3, I think we might be
ready to go with the last Maven 2 / Java 1.5 release. I am hoping that
Hervé or some other person would have a look and offer an opinion.
-
To unsubscribe, e-ma
Hi,
Although I strongly feel that SemVer [1] is the way to go when it
comes to versioning, I still haven't started using it though. That got
me thinking about why that is the case. I've come to the conclusion
that I'm lazy :)
It all comes down to tooling. Being accustomed to, and spoiled by,
usin
Looks like maven distribution gz is corrupted in your local repo. See if
removing ~/.m2/repository/org/apache/maven/apache-maven directory will
solve the problem for you. If not, file github issue like Jason suggested.
--
Regards,
Igor
On 2015-02-21 16:08, Cristiano Gavião wrote:
Hello,
I'm tr
On Mon, Feb 2, 2015 at 12:42 PM, Karl Heinz Marbaise wrote:
> Hi,
>
> after some discussions at FOSDEM with Hervé, Kristian and Robert in Brussels
> i will summarize some ideas we would like to share here:
>
> Make a final release of all plugins with minium Maven 2.2.1 (prerequisites)
> and Java 1
done.
On Fri, Feb 20, 2015 at 8:36 AM, Benson Margulies wrote:
> Whoops. Ok, I will deal over the weekend
>
> On Feb 20, 2015 8:26 AM, "Stuart McCulloch" wrote:
>>
>> I would, but I’m not a committer here ;)
>>
>> On Friday, 20 February 2015 at 13:15, Benson Margulies wrote:
>>
>> > I like your
Just create a Github issue and we'll take it there:
https://github.com/takari/takari-lifecycle
On Feb 21, 2015, at 4:08 PM, Cristiano Gavião wrote:
> Hello,
>
> I'm trying to learn how to use the new testing tools provided by takari.
> Started by the tests in takari-lifecycle-plugin-its from
Hello,
I'm trying to learn how to use the new testing tools provided by takari.
Started by the tests in takari-lifecycle-plugin-its from github master
branch.
but I'm getting errors when running the build. I'm using maven 3.2.5 in
linux with java 1.8.0_31:
Tests in error:
BasicTes
I've attached a patch for the rule usage.
Regards,Abhijit
From: social...@outlook.com
To: dev@maven.apache.org
Subject: RE: How to contribute new maven enforcer rules
Date: Sat, 21 Feb 2015 13:37:07 -0600
> First the use documentation would be great if you could provide it as a
> patch as well
Hi,
We solved 2 issues:
* Use instead of which has never
worked for maven-assembly-plugin
* MASFRES-9 Add pre-defined descriptor in
apache-source-release-assembly-descriptor for tarball-only
Staging repo:
https://repository.apache.org/content/repositories/orgapacheapache-1004/
https://repositor
> First the use documentation would be great if you could provide it as a
> patch as well...
I can do that. Just let me know the path to the existing documentation and I'll
attach a separate patch to the JIRA.
> Would it be possible to make two separate jira's for each of them? For
> each rule o
Hi,
On 2/21/15 7:43 PM, Abhijit Sarkar wrote:
Done. http://jira.codehaus.org/browse/MENFORCER-225
First looks good so far but i have two little things.
First the use documentation would be great if you could provide it as a
patch as well...
Ah...one other thing
Would it be possible to
Done. http://jira.codehaus.org/browse/MENFORCER-225
> Date: Sat, 21 Feb 2015 13:46:12 +0100
> From: khmarba...@gmx.de
> To: dev@maven.apache.org
> Subject: Re: How to contribute new maven enforcer rules
>
> Hi,
>
>
> On 2/20/15 8:55 PM, Abhijit Sarkar wrote:
> > Hi,I wrote 2 new enforces rules,
+1
On Feb 21, 2015, at 12:24 PM, Robert Scholte wrote:
> multiModuleProjectDirectory sounds indeed good enough
>
> Op Sat, 21 Feb 2015 17:48:10 +0100 schreef Igor Fedorenko
> :
>
>> Not sure. "top level" and "base" don't sound that much different to me.
>> And, frankly, don't add much clarify
multiModuleProjectDirectory sounds indeed good enough
Op Sat, 21 Feb 2015 17:48:10 +0100 schreef Igor Fedorenko
:
Not sure. "top level" and "base" don't sound that much different to me.
And, frankly, don't add much clarify to the term either. Maybe it should
be "multiModuleProjectDirectory",
Not sure. "top level" and "base" don't sound that much different to me.
And, frankly, don't add much clarify to the term either. Maybe it should
be "multiModuleProjectDirectory", i.e. without "base" or "top level"
adjective?
--
Regards,
Igor
On 2015-02-21 11:27, Robert Scholte wrote:
It's len
It's lengthly, but indeed better. And now that we don't care about its
length, how about TopLevelDirectory instead of BaseDirectory, just to
reflect that it is has nothing to with the location of uber module-parent
like in a flattened multimodule structure?
Robert
Op Sat, 21 Feb 2015 16:4
Correct. What I called "projectBaseDirectory" represents root directory
of a multimodule project. It is not related to parent/child relationship
among project modules. And it is not the same as "reactor base
directory" as it is currently implemented, but I agree reactor build
should behave like yo
Github user josephw closed the pull request at:
https://github.com/apache/maven/pull/38
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
Github user khmarbaise commented on the pull request:
https://github.com/apache/maven/pull/37#issuecomment-75376033
I would vote +1 for this ...;-)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Technically the reactor right now are the projects in modules from where you
start the build.
I think what this variable is trying to represent is the base directory of the
multi-module project. I would argue that, ultimately, the reactor base
directory should be the same as the multi-module p
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/37#issuecomment-75374322
I think this is reasonable, it should fail instead as it's incorrect.
Anyone have an issue merging this. All the ITs pass here so if there are no
objections today I'll merg
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/38#issuecomment-75373555
Committed. If it looks good to you close the pull request.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Op Sat, 21 Feb 2015 14:12:22 +0100 schreef Igor Fedorenko
:
On 2015-02-21 7:02, Robert Scholte wrote:
Hi Igor,
I agree that something like MNG-5767 can indeed help with the
experience.
Looking at the implementation I find the name projectBaseDirectory
confusing, I would have thought tha
+1
Op Wed, 18 Feb 2015 23:11:42 +0100 schreef Karl Heinz Marbaise
:
Hi,
We solved 11 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11250&version=16635
There are no issues left in JIRA:
http://jira.codehaus.org/browse/MREPOSITORY#selectedTab=com.atlassian.jira.plugin.sy
hi Julius,
first thanks for the patch
I have taken a look at it...
formatting looks ok...no problem to apply the patch...and checked...
On 2/20/15 8:56 PM, Julius Davies wrote:
Hi,
Just curious if anyone is interested in looking at this. I attached a
patch:
http://jira.codehaus.org/brow
On 2015-02-21 7:02, Robert Scholte wrote:
Hi Igor,
I agree that something like MNG-5767 can indeed help with the experience.
Looking at the implementation I find the name projectBaseDirectory
confusing, I would have thought that this is a per project(module)
baseDirectory.
We already have thin
Hi,
On 2/20/15 8:55 PM, Abhijit Sarkar wrote:
Hi,I wrote 2 new enforces rules, the ability to specify a set of
mutually-exclusive profiles (p1,p2:p1,p3 would mean p1 can't be active with
either p2 pr p3) and the ability to ban profiles (the contrary of
requireActiveProfile). Both of these su
On Sat, Feb 21, 2015 at 7:24 AM, Karl Heinz Marbaise wrote:
> https://repository.apache.org/content/repositories/maven-1138/org/apache/maven/plugins/maven-repository-plugin/2.4/maven-repository-plugin-2.4-source-release.zip
+1 binding.
Hi,
two more binding VOTE's needed...;-)
Kind regards
Karl Heinz Marbaise
On 2/18/15 11:11 PM, Karl Heinz Marbaise wrote:
Hi,
We solved 11 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11250&version=16635
There are no issues left in JIRA:
http://jira.codehaus.org/browse/
Hi Igor,
I agree that something like MNG-5767 can indeed help with the experience.
Looking at the implementation I find the name projectBaseDirectory
confusing, I would have thought that this is a per project(module)
baseDirectory.
We already have things like project.basedir and project.exe
Op Fri, 20 Feb 2015 04:48:54 +0100 schreef Hervé BOUTEMY
:
ok, I just updated the index page to try to improve explanations about
this
unusual/new toolchains use case (ie not trying to be consistent across
plugins)
notice that if you use ToolchainManagerPrivate like
maven-toolchains-plugi
Hi Hervé,
I actually wanted to revert this, because the reason is not 100% correct,
but I don't wonder if anyone will notice:
- the code itself can be built perfectly fine with JDK5.
- For the project using this plugin it requires at least JDK8 to *run the
maven-jdeps-plugin*, the project co
38 matches
Mail list logo
