GitHub user ChristianSchulte opened a pull request:
https://github.com/apache/maven/pull/21
[MNG-2199] Version ranges not supported for parent artifacts
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ChristianSchulte/maven
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/21#issuecomment-45974252
I have done several releases using 'release:prepare release:perform' with a
parent version range in use. The release plugin won't write the resolved parent
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/21#issuecomment-45980581
From what I can tell, release:prepare-with-pom should work the same way as
before. What this patch basically does is to resolve any parent version range
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/21#issuecomment-45980866
http://wiki.eclipse.org/Aether/New_and_Noteworthy#Version_Ranges
---
If your project is set up for it, you can reply to this email and have your
reply appear
GitHub user ChristianSchulte opened a pull request:
https://github.com/apache/maven-integration-testing/pull/7
[MNG-2199] Version ranges not supported for parent artifacts
Integration tests corresponding to Maven PR #21.
You can merge this pull request into a Git repository
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-46546268
Another option would be to provide support for activations based on some
language like:
activation
expressionOS IS 'Linux' AND ( PROPERTY 'Some Name
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-46547866
Could be as simple as:
```
activation
script engine-name= || extension= || mime-type=simple script
evaluating to a boolean/script
/activation
GitHub user ChristianSchulte opened a pull request:
https://github.com/apache/maven/pull/32
[MPIR-238] Addition of command line flag '--legacy-reactor-resolution'.
See http://jira.codehaus.org/browse/MPIR-238
This pull request will add a new command line flag
'--legacy
Github user ChristianSchulte closed the pull request at:
https://github.com/apache/maven/pull/32
---
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
GitHub user ChristianSchulte reopened a pull request:
https://github.com/apache/maven/pull/32
[MPIR-238] Addition of command line flag '--legacy-reactor-resolution'.
See http://jira.codehaus.org/browse/MPIR-238
This pull request will add a new command line flag
'--legacy
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-67438782
See http://jira.codehaus.org/browse/MNG-5738
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-67459407
Are you referring to
git rebase -i upstream/master
then squash all commits and push that ?
---
If your project is set up for it, you can
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-67605975
Rebased and then pushed.
---
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
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-67621081
I would need a way to disable workspace resolution mainly for the `site`
lifecycle.
cmd svn checkout .../tags/maven-3.0
cmd cd maven-3.0
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-67622663
It is re-enabling the following workflow in Maven 3.
cmd mvn release:prepare
cmd mvn release:perform
Wait until the artifacts
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-67625161
Maybe the proper solution would be to control this behaviour based on an
attribute of the lifecycle ? So a lifecycle can be flagged as producing
artifacts
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-67626029
Feeding the tagged sources to the reports is not an issue. Feeding
intermediate build results is. That's like the tagged sources changing with
every build
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-78290027
I totally agree with this. Do not cripple Maven to support bad ideas or
concepts. Supported by Maven as an indicator for something. Not supported by
Maven so
Github user ChristianSchulte closed the pull request at:
https://github.com/apache/maven/pull/32
---
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
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-78281257
@jvanzyl: You would not want the `test-jar` goal to package compiled test
classes instrumented by some reporting tool, would you ? So the forking logic
needs
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-78226219
I am really no fan of adding just another workaround.
@Jason: Are you suggesting to split site rendering from report data
generation ? So the build
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-77428933
I have no experience with the cobertura plugin. I just added
```
reportPlugin
groupIdorg.codehaus.mojo/groupId
artifactIdcobertura-maven
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-76933957
What's the state of the current head as of today ? I just wanted to test
the cobertura plugin but cannot build the site with Maven 3.2.6-SNAPSHOT due
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-75848081
I am still convinced that it is a good idea to allow Maven 3 'mvn
site-deploy' to work the same way as Maven 2. What's the issue with that ?
---
If your project
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-75990941
There are situations the behaviour is not wrong, in my opinion. Resolution
for non project `packaging` related lifecycles, for example. Maven could
detect
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-75794059
Regarding the recent discussion about releasing 3.2.6 as 3.3.0: Could this
be part of 3.3.0, please ?
---
If your project is set up for it, you can reply
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-76081933
Could not be more confusing.
Apache Maven is a software project management and comprehension tool. Based
on the concept of a project object model (POM
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-76122905
```
parent
module1
module2
```
With Maven 3 I need to
```
cmdcd parent mvn site-deploy -N cd module1 mvn site-deploy
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/50#issuecomment-165627334
Can you please 'rebase' the commit onto 'origin/master' so that I can merge
it without conflicts?
---
If your project is set up for it, you can reply
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/72#issuecomment-181984267
This has been committed. See MNG-5934. Please close this pull request
manually.
---
If your project is set up for it, you can reply to this email and have your
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/61#issuecomment-181983567
This has been committed. See MNG-5940. Please close this pull request
manually.
---
If your project is set up for it, you can reply to this email and have your
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/70#issuecomment-188009400
@barthel: See
[c31be833a6f8d9266990a708efe624d09fa06dec](https://github.com/ChristianSchulte/maven/commit/c31be833a6f8d9266990a708efe624d09fa06dec)
---
If your
GitHub user ChristianSchulte opened a pull request:
https://github.com/apache/maven-surefire/pull/144
Resource leaks.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ChristianSchulte/maven-surefire master
Alternatively you can
Github user ChristianSchulte commented on a diff in the pull request:
https://github.com/apache/maven-surefire/pull/144#discussion_r103110034
--- Diff:
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/report/ConsoleOutputFileReporter.java
---
@@ -69,8 +69,8
Github user ChristianSchulte commented on a diff in the pull request:
https://github.com/apache/maven-surefire/pull/144#discussion_r103110250
--- Diff:
surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java
---
@@ -236,13 +236,17 @@ private static void
Github user ChristianSchulte commented on a diff in the pull request:
https://github.com/apache/maven-surefire/pull/144#discussion_r103109929
--- Diff:
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/report/StatelessXmlReporter.java
---
@@ -240,6 +240,10
Github user ChristianSchulte commented on the issue:
https://github.com/apache/maven/pull/99
Could you please also provide an integration test against
[maven-integration-testing](https://github.com/apache/maven-integration-testing).
---
If your project is set up for it, you can
GitHub user ChristianSchulte opened a pull request:
https://github.com/apache/maven-integration-testing/pull/20
Integration tests for various JIRA issues.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ChristianSchulte/maven
GitHub user ChristianSchulte opened a pull request:
https://github.com/apache/maven/pull/107
Fixes to various JIRA issues.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ChristianSchulte/maven master
Alternatively you can
GitHub user ChristianSchulte opened a pull request:
https://github.com/apache/maven/pull/124
Make resolver debug log messages for projects and plugins consistent.
The graph returned by the resolver after resolution is logged at debug
level. This pull request only updates those
Github user ChristianSchulte commented on the issue:
https://github.com/apache/maven/pull/107
You'll need to merge the resolver bugfixes as well to make the IT work, of
course.
[MRESOLVER-8](https://github.com/ChristianSchulte/maven-resolver/commit
Github user ChristianSchulte commented on the issue:
https://github.com/apache/maven/pull/143
[Corresponding IT pull
request.](https://github.com/apache/maven-integration-testing/pull/27)
---
-
To unsubscribe, e
GitHub user ChristianSchulte opened a pull request:
https://github.com/apache/maven/pull/147
[MNG-5527] Dependency management import should support relocations.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ChristianSchulte
Github user ChristianSchulte commented on the issue:
https://github.com/apache/maven/pull/148
[Corresponding IT pull
request.](https://github.com/apache/maven-integration-testing/pull/30)
---
-
To unsubscribe, e
GitHub user ChristianSchulte opened a pull request:
https://github.com/apache/maven/pull/148
[MNG-5600] Dependency management import should support exclusions.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ChristianSchulte
GitHub user ChristianSchulte opened a pull request:
https://github.com/apache/maven/pull/146
[MNG-4463] Dependency management import should support version ranges.
Closes #64 without merging. ITs are pending to be committed.
You can merge this pull request into a Git repository
Github user ChristianSchulte commented on the issue:
https://github.com/apache/maven/pull/146
[Corresponding IT pull
request.](https://github.com/apache/maven-integration-testing/pull/28)
---
-
To unsubscribe, e
Github user ChristianSchulte commented on the issue:
https://github.com/apache/maven/pull/147
[Corresponding IT pull
request.](https://github.com/apache/maven-integration-testing/pull/29)
---
-
To unsubscribe, e
GitHub user ChristianSchulte opened a pull request:
https://github.com/apache/maven/pull/144
[MNG-2893] Update the DefaultPluginManager to not use a project depMaâ¦
â¦n for controlling it's transitive dependencies
You can merge this pull request into a Git repository by running
GitHub user ChristianSchulte opened a pull request:
https://github.com/apache/maven/pull/145
[MNG-6112] Central repository in the 4.0.0 super POM should declare uâ¦
â¦pdate policy 'never'.
You can merge this pull request into a Git repository by running:
$ git pull https
GitHub user ChristianSchulte opened a pull request:
https://github.com/apache/maven/pull/143
[MNG-5359] Declared execution in PluginMgmt gets bound to lifecycle (â¦
â¦regression)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
GitHub user ChristianSchulte opened a pull request:
https://github.com/apache/maven/pull/142
[MNG-6114] Profiles from the global settings should be ordered beforeâ¦
⦠profiles from the user settings.
You can merge this pull request into a Git repository by running:
$ git
GitHub user ChristianSchulte opened a pull request:
https://github.com/apache/maven/pull/141
[MNG-6164] Collections inconsistently immutable.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ChristianSchulte/maven MNG-6164
53 matches
Mail list logo
