[jira] [Commented] (MRELEASE-909) Add workItem/task support for scm deliver

[Deepti (JIRA)]

[ 
https://issues.apache.org/jira/browse/MRELEASE-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14996588#comment-14996588
 ] 

Deepti  commented on MRELEASE-909:
--

Could you please let us know when this will be added back and to which release. 

Thanks,

> Add workItem/task support for scm deliver
> -
>
> Key: MRELEASE-909
> URL: https://issues.apache.org/jira/browse/MRELEASE-909
> Project: Maven Release Plugin
>  Issue Type: Improvement
>  Components: prepare
>Affects Versions: 2.5.2
>Reporter: Chris Graham
>Assignee: Chris Graham
>  Labels: patch
> Attachments: Release-SCM-775.patch
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> Some SCMs (Jazz(RTC)/TFS/ClearCase etc) can support a mode where a workItem 
> or Task is required to be associated with changesets for a delivery operation 
> to work.
> The SCM-775 has the necessary work to support this feature (with the Jazz 
> provider as a starting point). This issue is the complimentary issue; the 
> changes in the release plugin needed to support calling the scm apis with 
> workItem support.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MEAR-216) Unable to include dependencies of type test-jar

[Karl Heinz Marbaise (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MEAR-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise updated MEAR-216:
-
Fix Version/s: (was: more-investigation)
   3.0.0

> Unable to include dependencies of type test-jar
> ---
>
> Key: MEAR-216
> URL: https://issues.apache.org/jira/browse/MEAR-216
> Project: Maven Ear Plugin
>  Issue Type: Improvement
>Affects Versions: 2.10
>Reporter: Maxim Frolov
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: test-jar-in-ear-2.zip, test-jar-in-ear.zip
>
>
> Please implement support for artifacts of type *test-jar*.
> One of the use cases would be to build a test EAR as a mix of production and 
> test JARs where the test JARs are used to set up the test data used to test 
> the production code.
> Currently including one or more dependencies of type test-jar causes 
> *LifecycleExecutionException*: 
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml 
> (default-generate-application-xml) on project suite-systemtests-common-ear: 
> Failed to initialize ear modules: Unknown artifact type[test-jar] for 
> artifact_id -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml 
> (default-generate-application-xml) on project suite-systemtests-common-ear: 
> Failed to initialize ear modules
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to 
> initialize ear modules
> at 
> org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:260)
> at 
> org.apache.maven.plugin.ear.GenerateApplicationXmlMojo.execute(GenerateApplicationXmlMojo.java:162)
> at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: org.apache.maven.plugin.ear.UnknownArtifactTypeException: Unknown 
> artifact type[test-jar] for common-domain-impl
> at 
> org.apache.maven.plugin.ear.EarModuleFactory.newEarModule(EarModuleFactory.java:88)
> at 
> org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:250)
> ... 22 more
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (MEAR-207) Remove the JavaModule/Ejb3Module which are marked deprecated

[Karl Heinz Marbaise (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MEAR-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise closed MEAR-207.

Resolution: Fixed
  Assignee: Karl Heinz Marbaise

Fixed in [r1713552|http://svn.apache.org/r1713552]

> Remove the JavaModule/Ejb3Module which are marked deprecated
> 
>
> Key: MEAR-207
> URL: https://issues.apache.org/jira/browse/MEAR-207
> Project: Maven Ear Plugin
>  Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0
>
>
> Removed the JavaModule which is marked deprecated and update the code 
> accordingly. Fail the build instead of warning.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MEAR-207) Remove the JavaModule/Ejb3Module which are marked deprecated

[Karl Heinz Marbaise (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MEAR-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise updated MEAR-207:
-
Description: Removed the JavaModule which is marked deprecated and update 
the code accordingly. Fail the build instead of warning.  (was: Removed the 
JavaModule which is marked deprecated and update the code accordingly. Fail the 
build instead of warning.
With the version 3.1 we can removed the code completely.)

> Remove the JavaModule/Ejb3Module which are marked deprecated
> 
>
> Key: MEAR-207
> URL: https://issues.apache.org/jira/browse/MEAR-207
> Project: Maven Ear Plugin
>  Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0
>
>
> Removed the JavaModule which is marked deprecated and update the code 
> accordingly. Fail the build instead of warning.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MEAR-207) Remove the JavaModule/Ejb3Module which are marked deprecated

[Karl Heinz Marbaise (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MEAR-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise updated MEAR-207:
-
Summary: Remove the JavaModule/Ejb3Module which are marked deprecated  
(was: Removed the JavaModule which is being marked deprecated)

> Remove the JavaModule/Ejb3Module which are marked deprecated
> 
>
> Key: MEAR-207
> URL: https://issues.apache.org/jira/browse/MEAR-207
> Project: Maven Ear Plugin
>  Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0
>
>
> Removed the JavaModule which is marked deprecated and update the code 
> accordingly. Fail the build instead of warning.
> With the version 3.1 we can removed the code completely.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MSHARED-461) Upgrade org.sonatype.aether to 1.13.1 / org.eclipse.aether 1.0.2.v20150114

[Karl Heinz Marbaise (JIRA)]

[ 
https://issues.apache.org/jira/browse/MSHARED-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14997080#comment-14997080
 ] 

Karl Heinz Marbaise commented on MSHARED-461:
-

Undone the change in [r1713506|http://svn.apache.org/r1713506]

> Upgrade org.sonatype.aether to 1.13.1 / org.eclipse.aether 1.0.2.v20150114
> --
>
> Key: MSHARED-461
> URL: https://issues.apache.org/jira/browse/MSHARED-461
> Project: Maven Shared Components
>  Issue Type: Improvement
>  Components: maven-common-artifact-filters
>Affects Versions: maven-common-artifact-filters-3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
> Fix For: maven-common-artifact-filters-3.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MNG-5840) is used if the groupId and artifactId match irrespective of the version

[Mukarram Baig (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14996943#comment-14996943
 ] 

Mukarram Baig commented on MNG-5840:


Hey guys,

I ran into a similar issue - I think 
(http://stackoverflow.com/questions/33613036/parent-pom-version-possibly-not-being-honored-by-mvn-3-3-3-for-properties-resolu)
 with 3.3.3 and I have noticed (and verified) it to be working correctly with 
3.3.9-SNAPSHOT, though not with 3.3.8. 

Can you please confirm if this is in fact available on 3.3.8? Please let me 
know if I should rather log a separate bug ticket for this use case?

Thanks!

>  is used if the groupId and artifactId match irrespective of 
> the version
> --
>
> Key: MNG-5840
> URL: https://issues.apache.org/jira/browse/MNG-5840
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.3.1, 3.3.3
>Reporter: Stephen Connolly
>Assignee: Stephen Connolly
>  Labels: regression
> Fix For: 3.3.8
>
> Attachments: mng-5840-testcase.tar.gz
>
>
> This is a regression. (In my view a serious one)
> Works fine with Maven 3.0 through 3.2.5
> Fails with 3.3.1 and 3.3.3



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MSHARED-461) Upgrade org.sonatype.aether to 1.13.1 / org.eclipse.aether 1.0.2.v20150114

[Karl Heinz Marbaise (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MSHARED-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise updated MSHARED-461:

Affects Version/s: (was: maven-common-artifact-filters-3.0.0)

> Upgrade org.sonatype.aether to 1.13.1 / org.eclipse.aether 1.0.2.v20150114
> --
>
> Key: MSHARED-461
> URL: https://issues.apache.org/jira/browse/MSHARED-461
> Project: Maven Shared Components
>  Issue Type: Improvement
>  Components: maven-common-artifact-filters
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MSHARED-461) Upgrade org.sonatype.aether to 1.13.1 / org.eclipse.aether 1.0.2.v20150114

[Karl Heinz Marbaise (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MSHARED-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise updated MSHARED-461:

Fix Version/s: (was: maven-common-artifact-filters-3.0.0)

> Upgrade org.sonatype.aether to 1.13.1 / org.eclipse.aether 1.0.2.v20150114
> --
>
> Key: MSHARED-461
> URL: https://issues.apache.org/jira/browse/MSHARED-461
> Project: Maven Shared Components
>  Issue Type: Improvement
>  Components: maven-common-artifact-filters
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MNG-5928) MBP excludes only one package from inlined embeded dependency

[Karl Heinz Marbaise (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14996775#comment-14996775
 ] 

Karl Heinz Marbaise commented on MNG-5928:
--

Can you please give a full example working project which shows the behaviour.

> MBP excludes only one package from inlined embeded dependency
> -
>
> Key: MNG-5928
> URL: https://issues.apache.org/jira/browse/MNG-5928
> Project: Maven
>  Issue Type: Bug
>  Components: Embedding
>Affects Versions: 3.2.1
> Environment: Windows 7, Java version: 1.7.0_71
>Reporter: Damyan
>
> Working:
> 
>   ;inline=!
> 
> Not working:
> 
>   ;inline=!|
> 
> Also not working when excluding package but inlining others packages.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SUREFIRE-1194) reporter argument does not work for TestNG

[Julien Herr (JIRA)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14998036#comment-14998036
 ] 

Julien Herr commented on SUREFIRE-1194:
---

Well, it won't be so easy:
* "-reporterlist" is available since 5.6 only
* "-reporterlist" is removed since 5.14.3, and replaced by "-reporter"
* "-reporter" is used since 5.6 too, but not in the method used by surefire. 
From `TestNGCommandLineArgs`:

```java
else if (REPORTER.equalsIgnoreCase(argv[i])) {
  if ((i + 1) < argv.length) {
ReporterConfig reporterConfig = ReporterConfig.deserialize(trim(argv[i + 
1]));
if (arguments.get(REPORTERS_LIST) == null) {
  arguments.put(REPORTERS_LIST, new ArrayList());
}
((List)arguments.get(REPORTERS_LIST)).add(reporterConfig);
i++;
  }
}
```

* `configure()` method used by the `MapConfigurator` is available since 5.5 
(currently surefire starts it at 5.10)
* remember SUREFIRE-1177, `configure()` should be replaced between 5.14 and 
5.14.2

What should I do?
* Quick fix for the current issue (what? how?), or
* Postpone the fix and fix it later with the configure migration?

> reporter argument does not work for TestNG
> --
>
> Key: SUREFIRE-1194
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1194
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: TestNG support
>Affects Versions: 2.19
>Reporter: Testo Nakada
>Assignee: Tibor Digana
> Fix For: 2.19.1
>
>
> TestNG plugin seems to map -reporter command line parameter to reporterslist 
> which was removed in TestNG project since 2010 
> (a4779524b59330e98ee596c5faa43ae1b33ff844). Therefore, this configuration has 
> stopped working since then. The configuration mentioned in 
> http://maven.apache.org/surefire/maven-surefire-plugin/examples/testng.html#Using_Custom_Listeners_and_Reporters
>  does not work as expected.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MEAR-208) Upgrade to Maven 3.0 compatiblity + JDK 6

[Karl Heinz Marbaise (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MEAR-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise updated MEAR-208:
-
Summary: Upgrade to Maven 3.0 compatiblity + JDK 6  (was: Upgrade to Maven 
3.0 compatiblity)

> Upgrade to Maven 3.0 compatiblity + JDK 6
> -
>
> Key: MEAR-208
> URL: https://issues.apache.org/jira/browse/MEAR-208
> Project: Maven Ear Plugin
>  Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
> Fix For: 3.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (MEAR-208) Upgrade to Maven 3.0 compatiblity + JDK 6

[Karl Heinz Marbaise (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MEAR-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise closed MEAR-208.

Resolution: Fixed
  Assignee: Karl Heinz Marbaise

Fixed in [r1713543|http://svn.apache.org/r1713543]

> Upgrade to Maven 3.0 compatiblity + JDK 6
> -
>
> Key: MEAR-208
> URL: https://issues.apache.org/jira/browse/MEAR-208
> Project: Maven Ear Plugin
>  Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
> Fix For: 3.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MNG-5928) MBP excludes only one package from inlined embeded dependency

[Damyan (JIRA)]

Damyan created MNG-5928:
---

 Summary: MBP excludes only one package from inlined embeded 
dependency
 Key: MNG-5928
 URL: https://issues.apache.org/jira/browse/MNG-5928
 Project: Maven
  Issue Type: Bug
  Components: Embedding
Affects Versions: 3.2.1
 Environment: Windows 7, Java version: 1.7.0_71
Reporter: Damyan


Working:

;inline=!


Not working:

;inline=!|!


Also not working when excluding package but inlining others packages.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SUREFIRE-1191) Run Single Test with Package Name Doesn't work

[Tibor Digana (JIRA)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14996339#comment-14996339
 ] 

Tibor Digana commented on SUREFIRE-1191:


[~agudian]
I have methods renaming and changes in ResolvedTest.
Later I would rename the class to ResolvedTestPattern but not in 2.19.1.
Let's make PR and we will focus on small scope of change.

> Run Single Test with Package Name Doesn't work
> --
>
> Key: SUREFIRE-1191
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1191
> Project: Maven Surefire
>  Issue Type: Wish
>Affects Versions: 2.19
>Reporter: Gunnar Schmidt
>Assignee: Andreas Gudian
> Fix For: 2.19.1
>
>
> Running the following command works:
> mvn test -Dtest=MyTestCaseTest#myTest
> This doesn't work (package name included):
> mvn test -Dtest=my.package.name.MyTestCaseTest#myTest



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SUREFIRE-1191) Run Single Test with Package Name Doesn't work

[Gunnar Schmidt (JIRA)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14996184#comment-14996184
 ] 

Gunnar Schmidt commented on SUREFIRE-1191:
--

Ok, I was just about to make a pull-request.. how about this one:
{code}
testClassFile = testClassFile.trim().replaceAll( "\\.(?=.*\\.)" , "/" );
{code}

> Run Single Test with Package Name Doesn't work
> --
>
> Key: SUREFIRE-1191
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1191
> Project: Maven Surefire
>  Issue Type: Wish
>Affects Versions: 2.19
>Reporter: Gunnar Schmidt
>Assignee: Andreas Gudian
> Fix For: 2.19.1
>
>
> Running the following command works:
> mvn test -Dtest=MyTestCaseTest#myTest
> This doesn't work (package name included):
> mvn test -Dtest=my.package.name.MyTestCaseTest#myTest



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SUREFIRE-1191) Run Single Test with Package Name Doesn't work

[Tibor Digana (JIRA)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14996201#comment-14996201
 ] 

Tibor Digana commented on SUREFIRE-1191:


Regex is too slow. Surefire slows down before starting first test because
it has too much work with pre-processing.

On Mon, Nov 9, 2015 at 9:14 AM, Gunnar Schmidt (JIRA) 



> Run Single Test with Package Name Doesn't work
> --
>
> Key: SUREFIRE-1191
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1191
> Project: Maven Surefire
>  Issue Type: Wish
>Affects Versions: 2.19
>Reporter: Gunnar Schmidt
>Assignee: Andreas Gudian
> Fix For: 2.19.1
>
>
> Running the following command works:
> mvn test -Dtest=MyTestCaseTest#myTest
> This doesn't work (package name included):
> mvn test -Dtest=my.package.name.MyTestCaseTest#myTest



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MNG-5928) MBP excludes only one package from inlined embeded dependency

[Damyan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNG-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Damyan updated MNG-5928:

Description: 
Working:

;inline=!


Not working:

;inline=!|


Also not working when excluding package but inlining others packages.

  was:
Working:

;inline=!


Not working:

;inline=!|!


Also not working when excluding package but inlining others packages.


> MBP excludes only one package from inlined embeded dependency
> -
>
> Key: MNG-5928
> URL: https://issues.apache.org/jira/browse/MNG-5928
> Project: Maven
>  Issue Type: Bug
>  Components: Embedding
>Affects Versions: 3.2.1
> Environment: Windows 7, Java version: 1.7.0_71
>Reporter: Damyan
>
> Working:
> 
>   ;inline=!
> 
> Not working:
> 
>   ;inline=!|
> 
> Also not working when excluding package but inlining others packages.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MWAR-358) Check if we need more support for web.xml entries

[Karl Heinz Marbaise (JIRA)]

Karl Heinz Marbaise created MWAR-358:


 Summary: Check if we need more support for web.xml entries
 Key: MWAR-358
 URL: https://issues.apache.org/jira/browse/MWAR-358
 Project: Maven WAR Plugin
  Issue Type: Improvement
Reporter: Karl Heinz Marbaise
Priority: Minor


https://docs.oracle.com/cd/E13222_01/wls/docs92/webapp/configureservlet.html ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)