This repo: https://github.com/airlift/resolver should have all you need.
The Presto engine uses it to discover and load plugins if necessary from
the local or remote repo. It uses the sonatype version of Aether, not the
current Apache Maven Artifact Resolver but my guess is that this is
straightfo
Hi,
[I discussed this on slack with @sjaranowski, he suggested to bring this
conversation here ]
The latest releases of the maven dependency plugin (3.2.0, 3.3.0)
introduced some changes in the way test dependencies are handled and
potentially flagged. Especially the "Non-test scoped test only de
g.
>
> What developers who choose to turn on this check want is simple: warn
> about any unnecessary dependency, including dependencies whose scope
> is too broad. That's what the plugin should do, and I *think* that's
> what it currently does.
>
> On Sun, May 1
Folks,
I am somewhat struggling to make integration tests pass for PRs. And it
seems that I am not alone. Looking at
https://github.com/apache/maven/commits/master, none of the merged commits
on master has successfully passed the test suite. It seems to have started
with the "[MNG-7353] ..." commi
re-its/core-it-suite/
> >
> > - looking at bootstrap output, it seems maven-dependency-plugin 3.1.1 is
> > available instead of 3.3.0 => I'll update the failing ITs and it should
> be
> > solved
> >
> > Regards,
> >
> > Hervé
> >
> &g
t;Core ITs Suite and Dependencies (incl.
> Plugins)"
> > of https://maven.apache.org/core-its/core-it-suite/
> >
> > - looking at bootstrap output, it seems maven-dependency-plugin 3.1.1 is
> > available instead of 3.3.0 => I'll update the failing ITs and it s
Team,
While tackling some issues around MNG-7529, I realized that there are
specific versions that can not be used for released artifacts. Specifically
any artifact whose version is shaped like the "SNAPSHOT_TIMESTAMP" format (
see
https://github.com/apache/maven-resolver/blob/master/maven-resolve
On Wed, Aug 31, 2022 at 3:33 AM Tamás Cservenák wrote:
I do not understand why you felt the need to insert this into the thread,
but just to be clear.
But a word of warning to avoid any misunderstanding: Maven (and ASF AFAIK,
> at least from 2010) was always "stable = RTC".
>
To avoid any misun
I would pretty much abandon anything pre-Java 6 at this point and
start moving towards Java 7 soon. The checkstyle plugin right now has
three open releases with only the third being really useful ("upgrade
to latest checkstyle") and given the previous release cadence it makes
me fear that this rele
t),
> we
> would get the best of every choice
>
> Regards,
>
> Hervé
>
> Le mardi 13 janvier 2015 19:52:35 Henning Schmiedehausen a écrit :
>> I would pretty much abandon anything pre-Java 6 at this point and
>> start moving towards Java 7 soon. The checkstyle
5+
years EOLed versions of Java).
-h
On Wed, Jan 14, 2015 at 11:08 AM, Henning Schmiedehausen
wrote:
> The 6.2 checkstyle requires java 7 and it also removes (!) at least
> one of the checks (RedundantThrows) which is used in all shipped
> checkstyle sets and one of the integration
Hi,
any chance to do a dependency plugin release?
Thanks,
Henning
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
I already did that. See https://github.com/apache/maven-plugins/pull/42
-h
On Sat, Jan 17, 2015 at 9:02 AM, Hervé BOUTEMY wrote:
> Le mercredi 14 janvier 2015 11:08:40 Henning Schmiedehausen a écrit :
>> The 6.2 checkstyle requires java 7 and it also removes (!) at least
>> on
MDEP-476 as a crucial feature that would help me a lot with the
basepom project.
-h
On Sat, Jan 17, 2015 at 12:40 AM, Karl Heinz Marbaise wrote:
> Hi,
>
> On 1/17/15 6:16 AM, Henning Schmiedehausen wrote:
>>
>> Hi,
>>
>> any chance to do a dependency plugin
default
> dependency, end-users can now upgrade the dependency when using the plugin
>
> Regards,
>
> Hervé
>
>
> Le samedi 17 janvier 2015 09:17:08 Henning Schmiedehausen a écrit :
>> I already did that. See https://github.com/apache/maven-plugins/pull/42
>>
&g
style Plugin in your
> project's POM.
>
> On Sat, Jan 17, 2015 at 6:39 PM, Henning Schmiedehausen
> wrote:
>> As long as I can just drop in 6.2 and the plugin does not break (as it
>> does today), I am fine.
>>
>> We are running our own checkstyle ruleset a
right now though to dig up the
>> jira.
>>
>> /Anders (mobile)
>>
>> Den 17 jan 2015 09:41 skrev "Karl Heinz Marbaise" > <mailto:khmarba...@gmx.de>>:
>>
>> Hi,
>>
>>
On Wed, Jan 21, 2015 at 11:49 PM, Dennis Lundberg wrote:
> On Thu, Jan 22, 2015 at 5:29 AM, Hervé BOUTEMY wrote:
>> Le mercredi 21 janvier 2015 14:44:27 Dennis Lundberg a écrit :
>>> There is some piece of code in Checkstyle 5.9 that uses Java 6+
>>> classes/methods. I don't remember where, but i
MPMD-368 is the most user visible problem with this plugin and the next
release should contain a fix for it. I tried 3.21.0 in our internal builds
and it still shows the same behavior as 3.20.0
I abstain from voting as there is no point in voting it down and I will not
vote this release up.
-h
O
Hi,
[I wanted to write about this for a while]
Maven has recently (3.9.x) started to log warning messages like this:
*[WARNING] Parameter 'localRepository' is deprecated core expression; Avoid
use of ArtifactRepository type. If you need access to local repository,
switch to '${repositorySystemSe
>From maven 3.9.2:
[WARNING] * org.basepom.maven:inline-maven-plugin:1.0.1
[WARNING] Declared at location(s):
[WARNING]* org.jdbi:jdbi3-core:3.38.3-SNAPSHOT (core/pom.xml) @ line 145
[WARNING] Used in module(s):
[WARNING]* org.jdbi:jdbi3-core:3.38.3-SNAPSHOT (core/pom.xml)
[WARNING]
Hi Tamas,
Thanks for the quick response.
On Fri, May 19, 2023 at 2:35 AM Tamás Cservenák wrote:
> Howdy,
>
> So, have a small local change, probably to go with 3.9.3.
>
[...]
> [WARNING] * org.basepom.maven:inline-maven-plugin:1.0.1
> [WARNING] Declared at location(s):
> [WARNING]* or
plugins I can update their versions, and then I still get the
> warnings, none of which I can do anything about. I can do something about
> compiler warnings, I can do nothing about these.
>
> I am left to explain up and down the food chain with hand handwaving why
> these warni
I put https://github.com/apache/maven/pull/1116 together which does exactly
that. It is literally three lines of code.
-h
On Fri, May 19, 2023 at 12:17 PM Henning Schmiedehausen <
henn...@schmiedehausen.org> wrote:
> Hi Gary,
>
> Seems we both work in similar places. :-) Loo
;default")
> >
> >
> >
> > On Fri, May 19, 2023 at 11:47 AM Gary Gregory
> > wrote:
> >
> > > From this user's POV, I feel these warning force me to spin my wheels:
> > If I
> > > have old plugins I can update their versions, a
Hi,
The page on https://maven.apache.org/resolver/maven-3.8.x.html states
that *"Since
version 1.7.0, Maven Resolver requires Java 8 to run and a brand new
default sync context factory has been implemented."*.
Assuming for a moment that Java 8+ is a no-brainer, what does the second
part of that s
On Sat, May 20, 2023 at 1:14 AM Michael Osipov wrote:
> Am 2023-05-20 um 00:35 schrieb Henning Schmiedehausen:
> > Hi,
> >
> > The page on https://maven.apache.org/resolver/maven-3.8.x.html states
> > that *"Since
> > version 1.7.0, Maven Resolver requires Jav
I have a plugin where the mojo implements Contextualizable and it does this:
@Override
public void contextualize(final Context context)
throws ContextException {
this.container = (PlexusContainer)
context.get(PlexusConstants.PLEXUS_KEY);
}
Basically, this gives me
Turns out that simply removing the method and annotating the field with
`@Inject` and adding sisu-plexus solved that for me.
-h
On Sun, May 21, 2023 at 3:37 PM Henning Schmiedehausen <
henn...@schmiedehausen.org> wrote:
> I have a plugin where the mojo implements Contextualizable an
maven 3.9.2:
mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean
install
[...]
current 3.9.3-SNAPSHOT:
mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean
install
[...]
*[WARNING] Invalid value specified for property maven.plugin.validation:
'BRIEF'. Supporte
od call, created https://issues.apache.org/jira/browse/MNG-7797
>
> Thanks
> T
>
> On Fri, May 26, 2023 at 10:09 PM Henning Schmiedehausen <
> henn...@schmiedehausen.org> wrote:
>
> > maven 3.9.2:
> >
> > mvn -DskipTests -Dmaven.plugin.validation=BRIEF
ews about
> 3.9.x just like you might be.
>
> While I understand your frustration about these threads (probably noise to
> you), please understand the intent behind these threads it as well.
>
> Thanks
> T
>
>
>
> On Sun, May 28, 2023 at 10:58 PM Henning Schmiedehausen &
To get this discussion a bit more back to actual substance:
Do you still need toolchains with JDK 11/17? I set the release version to
"8" (or anything else) in my builds, ripped out all the toolchains and it
"just works". We have done this for Jdbi for ages (require Java 11+ as the
build JDK; we e
I always assumed that Java versions are a solved problem in JDK 9+ with
'-release' which creates bytecode for the targeted JDK and even ensures
that no classes or methods from the JDK are used that are not supported in
that version.
There is a desire for "everything must be the same" that I am not
Agreed, that is one way to do that, but it seems to me that this is a
CI/integration test issue, not a build issue per se.
We do the same thing in Jdbi: Build with the LTS JDK, then test against 8,
11, 17, current Java release:
https://github.com/jdbi/jdbi/blob/master/.github/workflows/ci.yml
Per
Uhm, I have definitely gotten pushback when I ported some changes back to
the 3.8.x branch. The wording was (paraphrasing) "maven 3.8 is dead and we
do not plan to do any further releases, so don't add code to it". This was
with Maven 3.8.4 :-)
-h
On Wed, May 31, 2023 at 3:37 AM Guillaume Nodet
On Fri, Jun 9, 2023 at 7:44 AM Slawomir Jaranowski
wrote:
> In current 3.9.x we have:
>
> - NONE, // mute validation completely (validation issue collection still
> happens, it is just not reported!)
> - INLINE, // inline, each "internal" problem one line next to mojo
> invocation
> - SUMMARY,
Seems to work fine in my pipelines.
+1
The changed behavior for plugin validation should be documented; just
reading the release notes gives no clear indication what changed.
-h
(I can haz wrapper plugin and mvnd as well plz?)
On Fri, Jun 23, 2023 at 6:34 AM Tamás Cservenák wrote:
> Howdy,
>
The mail refers to -alpha-6 everywhere. but the subject says alpha-7.
-h
On Sat, Jun 24, 2023 at 3:57 AM Guillaume Nodet wrote:
> I'm starting a new vote to release this new alpha.
>
> 67 issues solved:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=123530
This is most likely a bot "warming up" by contributing to some well-known
(high-reputation) repository. Merging those will allow them to build a
reputation for things like "sell stars for github repos".
- https://the-guild.dev/blog/judging-open-source-by-github-stars
- https://dagster.io/blog/fake
tested my m6 regression and m7 works again.
+1
-h
On Tue, Jul 11, 2023 at 7:47 AM Guillaume Nodet wrote:
> I've staged a candidate release at
> https://dist.apache.org/repos/dist/dev/maven/mvnd/1.0-m7/
>
> This release provides distributions based on Maven 3.9.3 and 4.0.0-alpha-7
> releas
I have a large-ish project that builds JPMS "Automatic-Module-Name"
artifacts. At this point, I have the system to create per module javadocs
that use Java 9+ style (.../target/apidocs/{module.name}/module-summary.html
is the starting page).
Now I am trying to aggregate the various artifacts into
The sonatype nexus staging plugin at this point seems abandoned. Last
relevant commit/release was 17 months (!) ago, they killed the bug tracker
and removed all references to JIRA from the code.
The plugin does not work well in multi-module scenarios where the last
module does not commit an artifa
Hello fellow Maven & JPMS struggler!
I summarized the state of things for Jdbi here:
https://github.com/jdbi/jdbi/blob/master/JPMS-SUPPORT.md
My current belief is that there is no good path forward for projects to
transition from non-JPMS to JPMS unless you are willing to rework your
maven module
You will get zero participation in that case. I have one mailbox with my
mailing lists that I check from time to time. If a discussion is not there,
I will not go and look for it. Neither to a bug tracker (dozens of projects
and hundreds of issues with discussions) nor a chat system where tens of
c
I have a mixed kotlin/java multi-module project that uses src/main/java for
the java code and src/main/kotlin for kotlin code.
For the java-only projects, everything is fine. sourceDirectory points to
src/main/java, testSourceDirectory points to src/test/java.
We activate a specific profile that
On Sat, Sep 2, 2023 at 2:57 AM Martin Desruisseaux <
martin.desruisse...@geomatys.com> wrote:
> Hello Henning
>
> That migration would have been impossible with Maven, so we had to
> switch to Gradle. Even then it was difficult, but it could be made much
> easier with more adequate tooling support
spends a lot of time trying to deal with corner cases and I am not
sure that we get them right.
-h
On Sun, Sep 3, 2023 at 1:58 AM Martin Desruisseaux <
martin.desruisse...@geomatys.com> wrote:
> Le 2023-09-02 à 21 h 15, Henning Schmiedehausen a écrit :
>
> > This is
On Sun, Sep 3, 2023 at 11:19 PM Guillaume Nodet wrote:
> Le sam. 2 sept. 2023 à 08:16, Henning Schmiedehausen <
> henn...@schmiedehausen.org> a écrit :
>
> > I have a mixed kotlin/java multi-module project that uses src/main/java
> for
> > the java code and s
Hi,
We solved 16
issues:https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529&version=12352956
There are still a couple of issues left in
JIRA:https://issues.apache.org/jira/projects/MJAVADOC?filter=allopenissues
Staging
repo:https://repository.apache.org/content/repositori
obviously my +1
-h
On Mon, Sep 11, 2023 at 11:22 PM Henning Schmiedehausen <
henn...@schmiedehausen.org> wrote:
> Hi,
>
> We solved 16
> issues:https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529&version=12352956
>
> There are stil
epository "maven-1989 (staging: open)" [id=maven-1989] exists but is
> not exposed.
> Repository "maven-1989 (staging: open)" [id=maven-1989] exists but is not
> exposed.
>
Still need to push the key to the maven svn (ugh) repo.
-h
>
> TIA
> T
>
>
adoc450-static.jar
> I suppose these files should not be there, they are not in Git
>
> IMHO It does not deserve to drop the release, but we should dig into why
> this
> issue is happening now, it did not happen in the previous releases
>
> Regards,
>
> Hervé
>
> Le
Good call. Done.
-h
On Tue, Sep 12, 2023 at 11:08 AM Elliotte Rusty Harold
wrote:
> MJAVADOC-747 and MJAVADOC-764 are listed as blockers. Please
> reclassify these if they're not truly release blockers.
>
> On Tue, Sep 12, 2023 at 2:23 AM Henning Schmiedehausen
>
Hi,
The vote has passed with the following result:
+1 : henning, hboutemy, slachiewicz, cstamas, khmarbaise, sjaranowski
0 : -
-1: -
PMC quorum: hboutemy, slachiewicz, cstamas, khmarbaise, sjaranowski
I will promote the source release zip file to Apache distribution area and
the artifacts to t
The Apache Maven team is pleased to announce the release of the Apache
Maven Javadoc Plugin, version 3.6.0
The Javadoc Plugin uses the Javadoc tool to generate javadocs for the
specified project.
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your projec
The more I spend time with JPMS and maven, the more I wonder if we need to
have some kind of additional metadata for our dependency declarations.
Up until Java 8, dependencies were pretty straightforward: They go on the
classpath depending on their scope. Some are only on the compile classpath,
so
So I looked a bit more into that bug and why it crashes the way it crashes.
I also added this as a comment to the ticket but given the silence on most
tickets, I'd like to push for some discussion here on the mailing list.
I have two modules, core and testing (these are defined modules, they have
+1
Eyeballed it and did some basic testing on MacOS. All seems good here.
-h
On Sun, Oct 1, 2023 at 12:07 PM Tamás Cservenák wrote:
> Howdy,
>
> Note: This release completes the main goals of Maven 3.9.x lineage, among
> others moving to Java 8 and transition to latest Resolver 1.9.x features
I think we will need to start rethinking dependencies more. A similar
problem exists with modules; the current heuristics to decide whether a
dependency goes on module path or classpath will start to become painful in
the very near future.
-h
On Tue, Oct 17, 2023 at 10:05 PM Benjamin Marwell
wr
+1
-h
On Mon, Oct 16, 2023 at 3:50 PM Slawomir Jaranowski
wrote:
> Hi,
>
> - Last release was in 2015
> - use Maven 2.2.1
> - we have a Maven Plugin Tools - which should be one project for build and
> check Maven plugins
> - no active development ...
>
>
> https://issues.apache.org/jira/issues/
au
> > > @rmannibucau <https://twitter.com/rmannibucau> | Blog
> > > <https://rmannibucau.metawerx.net/> | Old Blog
> > > <http://rmannibucau.wordpress.com> | Github <
> > https://github.com/rmannibucau> |
> > > LinkedIn <https:
If the current standard type would be "dependency", this would work IMHO.
It is not. It is "jar". This is perceived as "packaging", not a specific
semantic type that represents "dependency").
A bom is "type == pom, scope == import" which is a special case. If this
were "type == bom, scope == impor
I don't understand fatjar and fatmodule. Why would we need that? How would
maven treat this different from a regular jar / module ?
-h
On Sun, Oct 29, 2023 at 8:10 AM Tamás Cservenák wrote:
> Howdy,
>
> The current draft of types we want to introduce (and packaging):
> https://gist.github.co
+1 to release.
Thanks,
Henning
On Mon, Mar 11, 2013 at 9:44 AM, John Casey wrote:
> Bump...
>
> Has this vote failed, then, or are we saying that all the +1's from the
> previous round of voting should be counted here? There is new code in this
> vote, so I'm not 100% sure that's a good
Hi,
any chance to do a maven release plugin release soon? 2.4 has the annoying
regression of not being able to deploy from a local repo (fixed in
MRELEASE-818) so either getting 2.4.1 or 2.5 would be really helpful.
Thanks,
Henning
Hi,
I finally was able to make heads and tails of the xdoc DTD as included
in the maven 1 xdoc plugin (thanks a lot for this, Lukas & Arnaud!) . To
make XMLMind to automatically identify these files, we do need a DTD
public identifier. Do you already have one? Googling for this didn't
really help
DOC-192, please make sure to resolve it before releasing
1.10
Best regards
Henning
>
> -Lukas
>
>
> Henning Schmiedehausen wrote:
> > Hi,
> >
> > I finally was able to make heads and tails of the xdoc DTD as included
> > in the
ea to publish it at this point. However, as far
> as I'm
> concerned, the xdoc-1.10 plugin could be released very soon,
> we will
> consider your demand as soon as it's done (please remind us if
> we
> forget, I know you a
Hi,
I have the following situation
Project A
project.xml
maven.xml, contains java:compile preGoal and postGoal
These are needed to compile project A.
Project B
extends Project A project.xml (because it shares the dependencies and
some more information)
maven.
Hi,
could someone please put this jar on ibiblio? Thanks.
Regards
Henning
>Path: news.hometree.net!not-for-mail
>From: Martin Cooper <[EMAIL PROTECTED]>
>Newsgroups: hometree.jakarta.announce
>Subject: [ANNOUNCEMENT] Commons FileUpload 1.0 Release Candidate 1 Released
>D
Hi,
to whom it may concern:
property names in maven (at least up to b9, don't know about b10) must
not contain "-". The torque plugin unfortunately contains two of these
which are promptly interpreted by jelly as .foo - bar.yyy instead
of .foo-bar.yyy
Please apply the attached patch to t
On Wed, 2005-08-03 at 10:02 +0200, Fabrizio Giustina wrote:
> On 8/2/05, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> > > Question: Is there documentation somewhere how you can influence the
> > > site build with your own style sheet? And which CSS tags must be
> > > defined for the site to build?
>
Hi,
I knew that this would come out wrong / will be read wrong.
a) I'm aware that this is not Jakarta. It is Maven. So rules are
probably different (I'm not on the Maven PMC, so all I know are the
public pages on maven.apache.org which is not really much. So I
considered the main apach
all the log information, you
must pull everything and pick. Unless you have a really, really long
changelog, that shouldn't really be a problem.
Best regards
Henning
>
> - Brett
>
> Henning Schmiedehausen wrote:
>
> >Hi,
> >
> >ah,
As a case in point, I am slowly moving the plugins that I maintain (
https://basepom.github.io/) to Java 17 and 21, even though these are Maven
3.x.x plugins. I will require projects that adopt those to use 17 or 21 to
run the build. Which is fine, because I can still deliver Java 8 or Java 11
comp
Is there a way to track which plugins are maven 3 only, maven 3/4 and maven
4 only? Would it make sense to add this to https://maven.apache.org/plugins/
?
-h
On Thu, May 15, 2025 at 11:22 PM Slawomir Jaranowski
wrote:
> The Apache Maven team is pleased to announce the release of the Apache
> M
On Fri, May 16, 2025 at 1:43 AM Vincent Potucek
wrote:
> Dear colleagues,
>
I am not your colleague.
Frankly, posting with a mail address of "me.com.invalid" makes me press
"Spam" usually right away. As this message has received some replies from
other developers, here is my take:
"Vendor spam
Big +1 to that. The maven 4 cycle has stretched for a long time and having
an actual release which can be targeted by the tool vendors would be a
great thing.
-h
On Wed, May 21, 2025 at 2:05 AM Guillaume Nodet wrote:
> Hi all,
>
> I have several significant features waiting as PRs (mixins and
[
http://jira.codehaus.org/browse/MPFILEACTIVITY-2?page=comments#action_56554 ]
Henning Schmiedehausen commented on MPFILEACTIVITY-2:
-
Any idea on the 1.6 release date?
> file activity plugin creates wrong links for Subvers
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03)
Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode)
Fedora Core 3 x86
Reporter: Henning Schmiedehausen
Assigned to: Arnaud Heritier
[EMAIL PROTECTED] maven-xdoc-plugin-1.9.1]$ echo $LANG
en_US
[EMAIL PROTECTED] maven-x
Type: Bug
Versions: 1.8.2
Reporter: Henning Schmiedehausen
Attachments: patch
We use client certificates for authentication to the web server which holds our
SVN repository. This results in the changelog messages containing the CN field
of the certificate; in my case e.g. it is
[ http://jira.codehaus.org/browse/MPCHANGELOG-70?page=all ]
Henning Schmiedehausen updated MPCHANGELOG-70:
--
Attachment: patch
patch vs. changelog-plugin 1.8.2 to fix the "space in usernames" issue.
> The Subversion parser
[ http://jira.codehaus.org/browse/MPXDOC-154?page=comments#action_45373 ]
Henning Schmiedehausen commented on MPXDOC-154:
---
Type the following instructions into a Linux command line:
svn checkout
http://svn.apache.org/repos/asf/maven/maven-1
Please upload village-2.0 to ibiblio
Key: MAVENUPLOAD-501
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-501
Project: maven-upload-requests
Type: Task
Reporter: Henning Schmiedehausen
http://www.softwareforge.de/projects
[
http://jira.codehaus.org/browse/MAVENUPLOAD-501?page=comments#action_45652 ]
Henning Schmiedehausen commented on MAVENUPLOAD-501:
http://www.ibiblio.org/maven/village/jars/
What part of "For projects with artifacts already upload
Jakarta Turbine has a maven plugin
--
Key: MAVEN-1687
URL: http://jira.codehaus.org/browse/MAVEN-1687
Project: Maven
Type: Task
Components: documentation
Reporter: Henning Schmiedehausen
Please add the following to the http
-plugin
Type: Bug
Versions: 1.7
Reporter: Henning Schmiedehausen
use the following unitTest definition in your POM:
**/*Test.java
**/Test*.java
**/test/*.java
[...]
When running under maven 1.0.2, all Test
Type: Bug
Components: core
Versions: 1.1-beta-2
Reporter: Henning Schmiedehausen
Consider the following POM snipped:
2.1
TURBINE_2_1
2.2
TURBINE_2_2_0
2.3-rc1
TURBINE_2_3_RC1
2.3-rc2
: core
Versions: 1.1-beta-2
Environment: java version "1.4.2_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-b05)
Java HotSpot(TM) Client VM (build 1.4.2_09-b05, mixed mode)
Fedora Core 3 Linux on x86
Reporter: Henning Schmiedehausen
Priority: Critical
A
Please create POM for javax.naming
--
Key: MAVENUPLOAD-521
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-521
Project: maven-upload-requests
Type: Wish
Reporter: Henning Schmiedehausen
Like some other POMs (javax.mail, javax.sql
Please update POM for javax.mail
Key: MAVENUPLOAD-522
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-522
Project: maven-upload-requests
Type: Wish
Reporter: Henning Schmiedehausen
javamail 1.3.3 is out:
4.0.0
javamail
Versions: 1.5.2
Reporter: Henning Schmiedehausen
Attachments: file-activity-report.html
The maven file-activity plugin creates wrong links at
docs/file-activity-report.html.
project.xml
scm:svn:http://svn.apache.org/repos/asf/jakarta/turbine/core/branches/TURBINE_2_3_BRANCH
Reporter: Henning Schmiedehausen
Attachments: changelog-report.html
The maven file-activity plugin creates wrong links at
docs/file-activity-report.html.
project.xml
scm:svn:http://svn.apache.org/repos/asf/jakarta/turbine/core/branches/TURBINE_2_3_BRANCH
scm:svn:https
Customize classpath when running tests
--
Key: MPTEST-57
URL: http://jira.codehaus.org/browse/MPTEST-57
Project: maven-test-plugin
Type: Improvement
Versions: 1.7
Reporter: Henning Schmiedehausen
Attachments
: Java(TM) 2 Runtime Environment, Standard Edition (build
1.4.2_07-b05)
Java HotSpot(TM) Client VM (build 1.4.2_07-b05, mixed mode)
Reporter: Henning Schmiedehausen
Attachments: maven-test.patch
(this is basically a rehash of MPTEST-16)
For porting unit tests from ant to maven, it was necessary
maven-changelog-plugin major rewrite
Key: MPCHANGELOG-60
URL: http://jira.codehaus.org/browse/MPCHANGELOG-60
Project: maven-changelog-plugin
Type: Improvement
Reporter: Henning Schmiedehausen
Attachments: changelog.patch
rewrite - scm support for xdoc plugin
-
Key: MPXDOC-134
URL: http://jira.codehaus.org/browse/MPXDOC-134
Project: maven-xdoc-plugin
Type: Improvement
Reporter: Henning Schmiedehausen
Assigned to: Arnaud HERITIER
Attachments
[
http://jira.codehaus.org/browse/MPCHECKSTYLE-29?page=comments#action_40759 ]
Henning Schmiedehausen commented on MPCHECKSTYLE-29:
(So the current lag seems to be six months?)
http://jakarta.apache.org/turbine/common/code
99 matches
Mail list logo
