Re: Create test jar during build without attaching

Thanks. That sounds perfect. Thanks, all, for your help. On Fri, Aug 19, 2016, 20:07 Guillaume Boué wrote: > Hi, > > It sounds like the simplest answer would be to use the > maven-assembly-plugin and generate the JAR in the > generate-test-resources phase. You can

Re: Create test jar during build without attaching

Hi, It sounds like the simplest answer would be to use the maven-assembly-plugin and generate the JAR in the generate-test-resources phase. You can configure the plugin not to attach the artifact with false. Then, still in the generate-test-resources phase, you bind an execution of

Re: Create test jar during build without attaching

Generate it during generateSources using a groovy script via gmaven? Or in Java within the test code itself? On Aug 19, 2016 4:21 PM, "Christopher" wrote: > We're not going to add the jar to SCM there's many reasons, and I could > go into depth about all of them (I've

Re: Create test jar during build without attaching

We're not going to add the jar to SCM there's many reasons, and I could go into depth about all of them (I've tried to enumerate some already), but again... that's not the question. We're not going to do that. and I've already stated that. I appreciate the advice... really, I do... but we're

Re: Create test jar during build without attaching

Hi Christopher, The point of this JAR is for use in a unit test, right? So if it's in src/test/resources, it will only end up lumped into the test JAR, not the main JAR. Do you guys deploy your test JAR for downstream consumption? If so, do you actually need all the unit tests to pass _when run

Replacement for org.apache.maven.monitor.event.EventDispatcher?

The EventDispatcher support was completely removed with the commit https://github.com/apache/maven/commit/505423e666b9a8814e1c1aa5d50f4e73b8d710f4 for Maven 3.0. Currently I instead use a JVM Shutdown Hook to

Re: Create test jar during build without attaching

We don't want to skip deployment of all the artifacts, just one jar built in one module for one test, which is not intended to be one of the artifact's modules. *maybe* we could move it to a separate module, and skip deploy, but we've already got a lot of module bloat, and I'd prefer not to make

Re: Create test jar during build without attaching

It is a test resource, built from source. I think it's substantively different from a jpg, because it is derived from the creative work (source code), and does not itself represent the creative work like a jpg does. Compiled code does not meet the definition of open source from the Open Source

Re: Create test jar during build without attaching

Perhaps I don't understand what is meant by "not attaching" but if all you want to do is skip deployment, the maven-deploy-plugin has this feature: true which can be added to the module you do not wish to deploy. We use this in order to not

Re: Create test jar during build without attaching

Confirmed. Is it so bad, though? :) I like the argument comparing putting .jpeg files in there. On Fri, Aug 19, 2016 at 2:13 PM, Christopher wrote: > src/test/resources are included in the source-release artifact, yes. > > On Fri, Aug 19, 2016 at 1:56 AM jieryn

Re: Create test jar during build without attaching

src/test/resources are included in the source-release artifact, yes. On Fri, Aug 19, 2016 at 1:56 AM jieryn wrote: > Would src/test/resources be included in the src artifact? I suspect not. > > On Thu, Aug 18, 2016 at 9:47 PM, Christopher wrote: > > If

Re: Create test jar during build without attaching

On Fri, Aug 19, 2016 at 1:38 PM Karl Heinz Marbaise wrote: > Hi, > > On 19/08/16 03:36, Christopher wrote: > > Hi Maven Users list, > > > > What's the best way to create a jar during a build without attaching it? > > > > Currently, our pom is configured to use the

Re: Create test jar during build without attaching

Hi, On 19/08/16 03:36, Christopher wrote: Hi Maven Users list, What's the best way to create a jar during a build without attaching it? Currently, our pom is configured to use the maven-jar-plugin to create it, but that plugin attaches an artifact, which gets deployed. We don't want that.

Re: Create test jar during build without attaching

I had the same need on a prior product, needed two jars to test the processing. After trying to find built-in Maven features/plugins to solve, including Embedder and other "Maven runners" I found with Google, I found the clearest and simplest approach was to make a nearly empty pom for each jar

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Hi Christian, This is awesome. == What works == With model version 4.0.0, Maven 3.4.0 now behaves exactly as before. And the property overriding bug no longer occurs, either. This maintains build reproducibility for my projects, for which I am very thankful. With model version 4.1.0, Maven

Replacement for org.apache.maven.monitor.event.EventDispatcher?

The EventDispatcher support was completely removed with the commit https://github.com/apache/maven/commit/505423e666b9a8814e1c1aa5d50f4e73b8d710f4 for Maven 3.0. Currently I instead use a JVM Shutdown Hook to perform some tasks at the end of the build which is not recommended either for obvious

Exchange data in memory between different mojo executions in different modules of the same plugin

To exchange data between several executions of my mojo I wanted to leverage AbstractMojo.getPluginContext(). Unfortunately although the map is being shared among multiple executions targeting the same project it is not shared among different projects in a multi-module build. Which API can I

Re: Create test jar during build without attaching

Hello Christopher, it seems the jar is a test resource, so it is not different from a jpg which could be included as well in this way IMO. Regards Mirko -- Sent from my mobile Am 19.08.2016 03:47 schrieb "Christopher" : If this were a personal project, I'd probably do

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Am 08/17/16 um 22:16 schrieb Curtis Rueden: > One question: for POM hierarchies with mixed model versions -- a 4.0.0 POM > which imports or extends a 4.1.0 POM or vice versa -- do you foresee any > complications? Parent and child need to use the same model version. There is no way to support

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

On Thu, Aug 18, 2016 at 5:24 PM, Curtis Rueden wrote: > Hi Stephane, > > > In fact, nowhere does it talk about what happens when dependencyManagement > comes in through both the parent and through imports. It does say, however: > I agree that both the doc and the code are