[ANN] Apache Maven JXR Plugin 3.0.0 Released
The Apache Maven team is pleased to announce the release of the Apache Maven JXR Plugin, version 3.0.0 The JXR Plugin produces a cross-reference of the project's sources. The generated reports make it easier for the user to reference or find specific lines of code. https://maven.apache.org/jxr/maven-jxr-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-jxr-plugin 3.0.0 You can download the appropriate sources etc. from the download page: https://maven.apache.org/jxr/download.cgi Release Notes - Maven JXR Plugin - Version 3.0.0 ** Bug * [JXR-68] - ignores classes with same name in other packages * [JXR-98] - Nested classes aren't linked correctly * [JXR-100] - Method declaration: using spaces before or after parenthesis prevents cross references generation * [JXR-126] - File write using platform default encoding * [JXR-135] - Invalid representation of inner class * [JXR-140] - Proper URL handling ** Improvement * [JXR-110] - Use equivalent css/images of javadoc * [JXR-124] - Remove excluded DEPENDENCIES file if new parent is used. * [JXR-125] - Upgrade to Maven 3.0 compatibility * [JXR-127] - Create anchor for classes generated from a Java source file * [JXR-131] - Reports 'jxr' and 'test-jxr' do not contain generated sources. * [JXR-132] - Aggregator reports should not require modules to be installed/deployed. ** Task * [JXR-134] - switch to Git NOTE: Special thanks for the contributions retrieved during the hackathon at JCreate. Enjoy, -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT] [VOTE] Release Apache Maven JXR Plugin version 3.0.0
Hi, The vote has passed with the following result: +1 : Karl Heinz Marbaise, Olivier Lamy, Jesper Udby, Tibor Digana, Hervé BOUTEMY, Robert Scholte PMC quorum: reached I will promote the artifacts to the central repo. On Sat, 22 Sep 2018 13:29:51 +0200, Robert Scholte wrote: Hi, We solved 18 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317527&version=12330848&styleName=Text There is still 1 issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317527%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1449/ https://repository.apache.org/content/repositories/maven-1449/org/apache/maven/jxr/jxr/3.0.0/jxr-3.0.0-source-release.zip Source release checksum(s): jxr-3.0.0-source-release.zip sha512: ccf691d97fa933030af58755fcf18678b7f4ed65b5ee4733e45cdbf023a51f755049fa3355e9d4aad8e78da510915695263f3363d517a2d562bc8780c765734b Staging site: https://maven.apache.org/jxr-archives/jxr-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Cut Maven Core Release 3.6.0
Hi Michael, On 25/09/18 08:07, Michael Osipov wrote: Am 2018-09-23 um 20:05 schrieb Karl Heinz Marbaise: Hi, based on the feedback we had I would like to announce to cut a release at the end of next Week which means (likely on Saturday/Sunday 29.09 / 30.09 )... If anyone has something which should be put into Maven core release the next week is your chance... So this time I'm stepping up to be release manager for 3.6.0 of Maven core...(if no one has objections to this.).. Currently maven master is fine ...so keep it green...ah...sorry blue ;-).. Kind regards Karl Heinz Marbaise On 13/09/18 22:20, Karl Heinz Marbaise wrote: Hi, based on the issues have been solved.. from my point of view waiting at the moment for the following issues: * MNG-6311 * MNG-6391 Afterwards I would like to cut a release of Maven Core... This results into the question: Should we call it 3.6.0 or 3.5.5..? Based on the fixed issues which are only bug fixes (my opinion)...I would vote for 3.5.5 ? What do you think? I'd like to upgrade Wagon [1] for this release. I will add SCM 1.11.1 to Wagon and start the release process today. If all is well, we can pick up the release by end of month. Is that ok? I don't see any issue here...cause I have claimed to do the release on Saturday / Sunday os in the end we might talk about a few days waiting... No problem at all.. Kind regards Karl Heinz Marbaise Michael [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20fixVersion%20%3D%203.2.0 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven JXR Plugin version 3.0.0
+1 On Sat, 22 Sep 2018 13:29:51 +0200, Robert Scholte wrote: Hi, We solved 18 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317527&version=12330848&styleName=Text There is still 1 issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317527%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1449/ https://repository.apache.org/content/repositories/maven-1449/org/apache/maven/jxr/jxr/3.0.0/jxr-3.0.0-source-release.zip Source release checksum(s): jxr-3.0.0-source-release.zip sha512: ccf691d97fa933030af58755fcf18678b7f4ed65b5ee4733e45cdbf023a51f755049fa3355e9d4aad8e78da510915695263f3363d517a2d562bc8780c765734b Staging site: https://maven.apache.org/jxr-archives/jxr-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Possible bug in the ProjectBuilder (3.5.4) ?
Ok, I found where the problem was... :-)
Certainly I do not set necessary objects to new instance of
ProjectBuildingRequest that I was doing.
Once I have reused the instance provided by the MavenSession instance,
the errors gone !
ProjectBuildingRequest request = session.getProjectBuildingRequest();
best regards,
Cristiano
On 24/09/2018 21:17, Cristiano wrote:
Hello, I need some assistance in order to identify whether the issue
I'm facing is a bug or a missing feature.
I'm adding a goal to my plugin that must read a POM project from a
repository and get details about the dependencies declared on it.
In order to build the POM object I've created the method below that
are using Core's org.apache.maven.project.ProjectBuilder:
public MavenProject loadProject(Artifact artifact,
MavenSession session,
boolean pResolveDependencies) throws
ProjectBuildingException {
ProjectBuildingRequest request = new
DefaultProjectBuildingRequest();
request.setLocalRepository(session.getLocalRepository());
request.setRemoteRepositories(
session.getCurrentProject().getRemoteArtifactRepositories());
request.setResolveDependencies(pResolveDependencies);
request.setRepositorySession(session.getRepositorySession());
request.setInactiveProfileIds(
Arrays.asList("when-building-java-using-java8")); ---> I
added this in order to try no get one of the errors reported.
return projectBuilder.build(artifact,
request).getProject();
}
In order to test it I'm trying to read this [pom]
https://search.maven.org/classic/#artifactdetails%7Cbr.com.c8tech.releng%7Cfpom-deps-felix%7C2.1%7Cpom.
This POM has declared a POM fragment:
br.com.c8tech.releng
2.1
fpom-deps-osgi
import
pom
And I'm using this code:
{
pom = loadProject(
new
DefaultArtifact("br.com.c8tech.releng:fpom-deps-felix:pom:2.1"),
true);
}
The error I'm getting from ProjectBuilder is about not being able
to get the versions declared in the imported POM ( declared in its
dependencyManagement) and also not being able to determine the
Java version of a profile activated by property.
Caused by: org.apache.maven.project.ProjectBuildingException:
Some problems were encountered while processing the POMs:
[ERROR] Failed to determine Java version for profile
when-building-java-using-java8 @
br.com.c8tech.releng:maven-parent-java:2.1,
/home/cvgaviao/.m2/repository/br/com/c8tech/releng/maven-parent-java/2.1/maven-parent-java-2.1.pom,
line 658, column 22
[ERROR] 'dependencies.dependency.version' for
net.java.dev.jna:jna:jar is missing. @
br.com.c8tech.releng:fpom-deps-felix:[unknown-version],
/home/cvgaviao/.m2/repository/br/com/c8tech/releng/fpom-deps-felix/2.1/fpom-deps-felix-2.1.pom,
line 329, column 21
[ERROR] 'dependencies.dependency.version' for
ch.qos.logback:logback-core:jar is missing. @
br.com.c8tech.releng:fpom-deps-felix:[unknown-version],
/home/cvgaviao/.m2/repository/br/com/c8tech/releng/fpom-deps-felix/2.1/fpom-deps-felix-2.1.pom,
line 337, column 21
could someone tell me if its a missing feature, a bug or maybe am I
missing something ?
thanks a lot,
Cristiano
