Had generation of the multi-module distribution binary zipfile working
yesterday.
Came back today to find I had apparently stepped on it before pushing.
Sigh. OK, I should be able to reproduce this, right?
Unfortunately, no. I'm missing something obvious again.
In context, currently broken
Duh. Just noticed that the FAQ explicitly mentions creating a child
module just to achieve this sequencing in multi-module projects. Mea
culpa, mea maxima culpa... I'd have hoped something could be done with
phase and target, but if not, not.
On 11/11/2023 11:44 AM, Joseph Kessselman wrote
On 11/11/2023 11:44 AM, Greg Chabala wrote:
Use the sourceReleaseAssemblyDescriptor of maven-assembly-plugin:
https://maven.apache.org/apache-resource-bundles/source-release/
Thanks; hadn't seen that one. Definitely a fan of not reinventing wheels.
Can that be configured to write the archives
Sorry:
https://github.com/apache/xalan-java/tree/xalan-java-mvn-refactored
(which currently has the binary assembly commented out).
Dependency order... Well, I'm currently running the assembly at the top
level, which would presumably mean it has to run after packaging of the
contained
beaten into
my head.
Checked in on xalan-java branch xalan-java-mvn-refactored with bin
assembly commented out, if anyone wants to see it in context.
On 11/10/2023 9:37 PM, Joseph Kessselman wrote:
Oh. I probably forgot to set dependencies. Checking.
On 11/10/2023 9:35 PM, Joseph Kessselman
Oh. I probably forgot to set dependencies. Checking.
On 11/10/2023 9:35 PM, Joseph Kessselman wrote:
I'm trying to adapt the examples given at
https://maven.apache.org/plugins/maven-assembly-plugin to work with my
multi-module project.
Source was mostly easy -- I copied the into a file
I'm trying to adapt the examples given at
https://maven.apache.org/plugins/maven-assembly-plugin to work with my
multi-module project.
Source was mostly easy -- I copied the into a file, tweaked
its excludes (still wish it picked up the .gitinclude automagically),
and it worked. I'd still
... Actually, correction -- not the jar plugin, the assembly plugin. (sigh)
On 11/10/2023 1:42 PM, Joseph Kessselman wrote:
(Or, equivalently be told to take exclude list from a file in .gitignore
syntax and then be told .gitignore was that file.)
If not, I'd consider that worth adding
(Or, equivalently be told to take exclude list from a file in .gitignore
syntax and then be told .gitignore was that file.)
If not, I'd consider that worth adding.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For obvious reasons, if would be nice if the -version option on my
project automatically reported the version I'd set in the pom.xml rather
than my trying to synchronize the two manually.
The best approaches I've found so far are in
Right. Copypaste of the plugin doesn't work because Maven is declarative.
One instance of exec-maven-plugin with multiple s, each
having its own ID (since the default is to collide) and its own set of
arguments, appears to be what's intended.
Unfortunately only the first seems to be
, Joseph Kessselman wrote:
Turns out Stylebook does have a front-end driver that I don't have
source for, so I'm just invoking it via exec:java for now. I'll clean up
later. At least it gets rid of the platform-specific script and puts the
pom in charge of everything.
Quick question re exec-maven
for one instance of
the plugin to run multiple executions, or should I just rely on copypasta?
On 11/4/2023 7:53 PM, Joseph Kessselman wrote:
1) For backward compatibility with the prior Ant build (and with the
test framework's assumptions about where compiled code will land), I
have my maven
1) For backward compatibility with the prior Ant build (and with the
test framework's assumptions about where compiled code will land), I
have my maven build creating ./build/ in the top-level directory and
copying the jarfiles from the individual modules up to that using
I've just issued a pull request proposing that the Apache Xalan-Java
project cut over from Ant-based to Maven-based build.
This is the first time I'm working with Maven, and I'm *sure* I have
done things that are bad form. If anyone has time and energy to glance
at it and sanity-check that I
Oh. Duh.
com.sun
tools
1.6.0
system
${toolsjar}
On 10/3/2023 10:04 PM, Alexander Kriegisch wrote:
Hi Joseph.
I think you uncovered a bug in Maven Javadoc Plugin. I just created
https://issues.apache.org/jira/browse/MJAVADOC-775 on your
Hi, folks. I'm in the process of trying to port the Apache Xalan build
from Ant to Maven. It's close to usable, but I'm still struggling with a
few odd corners.
One of the odder corners: The Xalan documentation uses a javadoc taglet,
@xsl.usage, to indicate whether a method is intended only
17 matches
Mail list logo
