[jira] [Commented] (MNG-7045) Drop CDI API from Maven

[ https://issues.apache.org/jira/browse/MNG-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17243488#comment-17243488 ] Mark Struberg commented on MNG-7045: +1 I was opposed to even the atinject and slf4j apis back then.

[jira] [Commented] (MSHADE-342) Many integration tests fail when run in isolation

[ https://issues.apache.org/jira/browse/MSHADE-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17006435#comment-17006435 ] Mark Struberg commented on MSHADE-342: -- I've documented the proper usage over at MASSEMBLY-919. You

[jira] [Commented] (MASSEMBLY-775) Emit WARNING instead of ERROR

[ https://issues.apache.org/jira/browse/MASSEMBLY-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003278#comment-17003278 ] Mark Struberg commented on MASSEMBLY-775: - proposed change up for review

[jira] [Comment Edited] (MASSEMBLY-775) Emit WARNING instead of ERROR

[ https://issues.apache.org/jira/browse/MASSEMBLY-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002950#comment-17002950 ] Mark Struberg edited comment on MASSEMBLY-775 at 12/24/19 5:52 PM: ---

[jira] [Commented] (MASSEMBLY-775) Emit WARNING instead of ERROR

[ https://issues.apache.org/jira/browse/MASSEMBLY-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002950#comment-17002950 ] Mark Struberg commented on MASSEMBLY-775: - Yea, the problem is not really the WARN or ERROR.

[jira] [Commented] (MASSEMBLY-775) Emit WARNING instead of ERROR

[ https://issues.apache.org/jira/browse/MASSEMBLY-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002881#comment-17002881 ] Mark Struberg commented on MASSEMBLY-775: - There are actual that a {{/}} is interpreted as

[jira] [Commented] (MASSEMBLY-775) Emit WARNING instead of ERROR

[ https://issues.apache.org/jira/browse/MASSEMBLY-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002759#comment-17002759 ] Mark Struberg commented on MASSEMBLY-775: - It looks like the IT for MASSEMBLY-665 doesn't

[jira] [Comment Edited] (MASSEMBLY-775) Emit WARNING instead of ERROR

[ https://issues.apache.org/jira/browse/MASSEMBLY-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002164#comment-17002164 ] Mark Struberg edited comment on MASSEMBLY-775 at 12/23/19 8:45 AM: ---

[jira] [Comment Edited] (MASSEMBLY-775) Emit WARNING instead of ERROR

[ https://issues.apache.org/jira/browse/MASSEMBLY-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002162#comment-17002162 ] Mark Struberg edited comment on MASSEMBLY-775 at 12/23/19 8:45 AM: ---

[jira] [Commented] (MASSEMBLY-775) Emit WARNING instead of ERROR

[ https://issues.apache.org/jira/browse/MASSEMBLY-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002164#comment-17002164 ] Mark Struberg commented on MASSEMBLY-775: - the original ticket that introduced all those

[jira] [Commented] (MASSEMBLY-775) Emit WARNING instead of ERROR

[ https://issues.apache.org/jira/browse/MASSEMBLY-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002162#comment-17002162 ] Mark Struberg commented on MASSEMBLY-775: - this ticket applied the warnForPlatformSpecifics

[jira] [Assigned] (MSHADE-286) Artifacts to be included for shading are not consistently checked for existence

[ https://issues.apache.org/jira/browse/MSHADE-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned MSHADE-286: Assignee: Mark Struberg > Artifacts to be included for shading are not consistently

[jira] [Commented] (MASSEMBLY-919) Transitive dependency of a test dependency is included

[ https://issues.apache.org/jira/browse/MASSEMBLY-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000165#comment-17000165 ] Mark Struberg commented on MASSEMBLY-919: - I was not able to reproduce your problem. I've now

[jira] [Assigned] (MASSEMBLY-919) Transitive dependency of a test dependency is included

[ https://issues.apache.org/jira/browse/MASSEMBLY-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned MASSEMBLY-919: --- Assignee: Mark Struberg > Transitive dependency of a test dependency is included

[jira] [Resolved] (MSHADE-337) Relocation cannot process class file version 58 JARs

[ https://issues.apache.org/jira/browse/MSHADE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved MSHADE-337. -- Fix Version/s: 3.2.2 Resolution: Fixed > Relocation cannot process class file version

[jira] [Commented] (MSHADE-337) Relocation cannot process class file version 58 JARs

[ https://issues.apache.org/jira/browse/MSHADE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16998610#comment-16998610 ] Mark Struberg commented on MSHADE-337: -- asmVersion already got updated to 7.2 in commit

[jira] [Resolved] (MSHADE-285) It should be possible to shade test sources as a JAR

[ https://issues.apache.org/jira/browse/MSHADE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved MSHADE-285. -- Fix Version/s: 3.2.2 Resolution: Fixed Thanks again Peter, excellent stuff! > It

[jira] [Assigned] (MSHADE-285) It should be possible to shade test sources as a JAR

[ https://issues.apache.org/jira/browse/MSHADE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned MSHADE-285: Assignee: Mark Struberg > It should be possible to shade test sources as a JAR >

[jira] [Resolved] (MSHADE-284) Shaded test JARs are always empty

[ https://issues.apache.org/jira/browse/MSHADE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved MSHADE-284. -- Fix Version/s: 3.2.2 Resolution: Fixed PR applied, thanks a lot, Peter! > Shaded test

[jira] [Assigned] (MSHADE-284) Shaded test JARs are always empty

[ https://issues.apache.org/jira/browse/MSHADE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned MSHADE-284: Assignee: Mark Struberg > Shaded test JARs are always empty >

[jira] [Commented] (MSHADE-284) Shaded test JARs are always empty

[ https://issues.apache.org/jira/browse/MSHADE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16997413#comment-16997413 ] Mark Struberg commented on MSHADE-284: -- I'll gonna look into it tonight or in the next 2 days. >

[jira] [Comment Edited] (SUREFIRE-1457) trimStackTrace should be disabled by default

[ https://issues.apache.org/jira/browse/SUREFIRE-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493318#comment-16493318 ] Mark Struberg edited comment on SUREFIRE-1457 at 5/29/18 9:56 AM: -- +1

[jira] [Commented] (SUREFIRE-1457) trimStackTrace should be disabled by default

[ https://issues.apache.org/jira/browse/SUREFIRE-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493318#comment-16493318 ] Mark Struberg commented on SUREFIRE-1457: - +1 to disable it and go back to the original

[jira] [Comment Edited] (MJAVADOC-494) javadoc:aggregate ignores repositories declared in sub-modules

[ https://issues.apache.org/jira/browse/MJAVADOC-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16191844#comment-16191844 ] Mark Struberg edited comment on MJAVADOC-494 at 10/4/17 7:10 PM: -

[jira] [Comment Edited] (MJAVADOC-494) javadoc:aggregate ignores repositories declared in sub-modules

[ https://issues.apache.org/jira/browse/MJAVADOC-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16191844#comment-16191844 ] Mark Struberg edited comment on MJAVADOC-494 at 10/4/17 7:09 PM: -

[jira] [Commented] (MJAVADOC-494) javadoc:aggregate ignores repositories declared in sub-modules

[ https://issues.apache.org/jira/browse/MJAVADOC-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16191844#comment-16191844 ] Mark Struberg commented on MJAVADOC-494: verified with maven-3.3.9 and

[jira] [Commented] (MNG-6082) Introduction of model version 4.1.0

[ https://issues.apache.org/jira/browse/MNG-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15746401#comment-15746401 ] Mark Struberg commented on MNG-6082: Well, I didn't want to offend anyone. It seems that a lot of work

[jira] [Comment Edited] (MNG-6082) Introduction of model version 4.1.0

[ https://issues.apache.org/jira/browse/MNG-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15746028#comment-15746028 ] Mark Struberg edited comment on MNG-6082 at 12/13/16 7:53 PM: -- *edit because it

[jira] [Commented] (MNG-6082) Introduction of model version 4.1.0

[ https://issues.apache.org/jira/browse/MNG-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15746028#comment-15746028 ] Mark Struberg commented on MNG-6082: just a general observation. Such a jira entry is imo totally

[jira] [Commented] (MNG-5649) Stop abusing IllegalArgumentException in case of null and use Guava's Preconditions

[ https://issues.apache.org/jira/browse/MNG-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14954676#comment-14954676 ] Mark Struberg commented on MNG-5649: -1 for using Guava all over. I've used in in the past and it turned

[jira] (MRELEASE-767) releasing flat multi-module projects using git

[ https://jira.codehaus.org/browse/MRELEASE-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed MRELEASE-767. -- Resolution: Fixed Fix Version/s: 2.5 indeed, thanks for testing it! releasing flat

[jira] (SCM-740) Maven Release Plugin releases SNAPSHOT instead of STABLE version

[ https://jira.codehaus.org/browse/SCM-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed SCM-740. - Resolution: Fixed Fix Version/s: 1.10 Assignee: Mark Struberg patch applied with small cleanup.

[jira] (MCHECKSTYLE-166) Drop @requiresDependencyResolution test

[ https://jira.codehaus.org/browse/MCHECKSTYLE-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed MCHECKSTYLE-166. - Resolution: Won't Fix Assignee: Mark Struberg The maven-checkstyle-plugin supports

[jira] (MCHECKSTYLE-89) java.lang.RuntimeException: Unable to get class information for XXXException

[ https://jira.codehaus.org/browse/MCHECKSTYLE-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed MCHECKSTYLE-89. Resolution: Not A Bug This is not a bug of the maven-checkstyle-plugin but might be a

[jira] (MCHECKSTYLE-89) java.lang.RuntimeException: Unable to get class information for XXXException

[ https://jira.codehaus.org/browse/MCHECKSTYLE-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned MCHECKSTYLE-89: Assignee: Mark Struberg java.lang.RuntimeException: Unable to get class

[jira] (MCHECKSTYLE-207) file handle leak - leading to failed builds

[ https://jira.codehaus.org/browse/MCHECKSTYLE-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=342256#comment-342256 ] Mark Struberg commented on MCHECKSTYLE-207: --- Any update on this, Dennis? Would like

[jira] (MCHECKSTYLE-211) allow inline configuration for checkstyle plugin

[ https://jira.codehaus.org/browse/MCHECKSTYLE-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned MCHECKSTYLE-211: - Assignee: Mark Struberg allow inline configuration for checkstyle plugin

[jira] (MCHECKSTYLE-211) allow inline configuration for checkstyle plugin

[ https://jira.codehaus.org/browse/MCHECKSTYLE-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=342205#comment-342205 ] Mark Struberg commented on MCHECKSTYLE-211: --- Working on a way to implement this

[jira] (MCHECKSTYLE-211) allow inline configuration for checkstyle plugin

[ https://jira.codehaus.org/browse/MCHECKSTYLE-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed MCHECKSTYLE-211. - Resolution: Fixed Fix Version/s: 2.12 fixed in a similar way than suggested by

[jira] (MCHECKSTYLE-111) More information on issue: Got an exception - java.lang.RuntimeException: Unable to get class information for [exception]

[ https://jira.codehaus.org/browse/MCHECKSTYLE-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed MCHECKSTYLE-111. - Resolution: Not A Bug Fix Version/s: 2.12 Assignee: Mark Struberg

[jira] (MCHECKSTYLE-211) allow inline configuration for checkstyle plugin

[ https://jira.codehaus.org/browse/MCHECKSTYLE-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=341742#comment-341742 ] Mark Struberg commented on MCHECKSTYLE-211: --- great idea. That way one can enable the

[jira] (SCM-714) mvn release:prepare fails if the command line is too long on windows

[ https://jira.codehaus.org/browse/SCM-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323287#comment-323287 ] Mark Struberg commented on SCM-714: --- Hi Felix! Please note that scm:add != git-add and scm:checkin

[jira] (SCM-538) mvn reactor:make-scm-changes fails for git provider with local git index

[ https://jira.codehaus.org/browse/SCM-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed SCM-538. - Resolution: Not A Bug we still got no answer whether the url really was file:.. or if the two dots were just a

[jira] (MRELEASE-831) sometimes the version suggestion for the SCM tag doesnt work in release:prepare

Mark Struberg created MRELEASE-831: -- Summary: sometimes the version suggestion for the SCM tag doesnt work in release:prepare Key: MRELEASE-831 URL: https://jira.codehaus.org/browse/MRELEASE-831

[jira] (MRELEASE-831) sometimes the version suggestion for the SCM tag doesnt work in release:prepare

[ https://jira.codehaus.org/browse/MRELEASE-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=322043#comment-322043 ] Mark Struberg commented on MRELEASE-831: nope, the release version is 1.1.8 as with all

[jira] (MRELEASE-777) release plugin shouldn't git clone if the SCM is git

[ https://jira.codehaus.org/browse/MRELEASE-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317639#comment-317639 ] Mark Struberg commented on MRELEASE-777: hi Fred! If you use GIT, then please use the

[jira] (MRELEASE-777) release plugin shouldn't git clone if the SCM is git

[ https://jira.codehaus.org/browse/MRELEASE-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317644#comment-317644 ] Mark Struberg commented on MRELEASE-777: being a GIT user/contributor since 2006 I can

[jira] (MSHARED-252) drop XmlReader and only use XmlStreamReader

[ https://jira.codehaus.org/browse/MSHARED-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed MSHARED-252. - Resolution: Fixed Fix Version/s: maven-shared-utils-0.1 drop XmlReader and only use

[jira] (MSHARED-236) Refactor utility classes of shared components into an own utility package

[ https://jira.codehaus.org/browse/MSHARED-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed MSHARED-236. - Resolution: Fixed Fix Version/s: maven-shared-utils-0.1 Almost all important p-u classes are

[jira] (MSHARED-252) drop XmlReader and only use XmlStreamReader

Mark Struberg created MSHARED-252: - Summary: drop XmlReader and only use XmlStreamReader Key: MSHARED-252 URL: https://jira.codehaus.org/browse/MSHARED-252 Project: Maven Shared Components

[jira] (MSHARED-252) drop XmlReader and only use XmlStreamReader

[ https://jira.codehaus.org/browse/MSHARED-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned MSHARED-252: - Assignee: Mark Struberg drop XmlReader and only use XmlStreamReader

[jira] (MSHARED-238) [DirectoryScanner] introduce a way to abort scanning if a certain criteria is met

[ https://jira.codehaus.org/browse/MSHARED-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated MSHARED-238: -- Component/s: maven-shared-utils [DirectoryScanner] introduce a way to abort scanning if a

[jira] (MSHARED-238) [DirectoryScanner] introduce a way to abort scanning if a certain criteria is met

[ https://jira.codehaus.org/browse/MSHARED-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed MSHARED-238. - Resolution: Fixed Fix Version/s: maven-shared-utils-0.1 [DirectoryScanner] introduce a

[jira] (MRELEASE-777) release plugin shouldn't git clone if the SCM is git

[ https://jira.codehaus.org/browse/MRELEASE-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed MRELEASE-777. -- Resolution: Not A Bug There are config options for this exact scenario

[jira] (MCOMPILER-179) Warnings

[ https://jira.codehaus.org/browse/MCOMPILER-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=309531#comment-309531 ] Mark Struberg commented on MCOMPILER-179: - temporarily set plexus-compiler back to 1.9.1

[jira] (MSHARED-244) Add EMPTY_xxxx_ARRAY from commons-lang to our CollectionsUtils

Mark Struberg created MSHARED-244: - Summary: Add EMPTY__ARRAY from commons-lang to our CollectionsUtils Key: MSHARED-244 URL: https://jira.codehaus.org/browse/MSHARED-244 Project: Maven Shared

[jira] (MSHARED-244) Add EMPTY_xxxx_ARRAY from commons-lang to our CollectionsUtils

[ https://jira.codehaus.org/browse/MSHARED-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned MSHARED-244: - Assignee: Mark Struberg Add EMPTY__ARRAY from commons-lang to our CollectionsUtils

[jira] (MSHARED-244) Add EMPTY_xxxx_ARRAY from commons-lang to our CollectionsUtils

[ https://jira.codehaus.org/browse/MSHARED-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed MSHARED-244. - Resolution: Fixed fixed in r1388452 by adding an ArrayUtils class with the constants taken from

[jira] (MSHARED-245) add IncrementalBuildHelper

Mark Struberg created MSHARED-245: - Summary: add IncrementalBuildHelper Key: MSHARED-245 URL: https://jira.codehaus.org/browse/MSHARED-245 Project: Maven Shared Components Issue Type: New

[jira] (MSHARED-245) add IncrementalBuildHelper

[ https://jira.codehaus.org/browse/MSHARED-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=309441#comment-309441 ] Mark Struberg commented on MSHARED-245: --- initial version committed in r1388456. Tests are

[jira] (MSHARED-244) Add EMPTY_xxxx_ARRAY from commons-lang to our CollectionsUtils

[ https://jira.codehaus.org/browse/MSHARED-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=309477#comment-309477 ] Mark Struberg commented on MSHARED-244: --- The reason is pretty simple: binary compatibility!

[jira] (MSHARED-244) Add EMPTY_xxxx_ARRAY from commons-lang to our CollectionsUtils

[ https://jira.codehaus.org/browse/MSHARED-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=309491#comment-309491 ] Mark Struberg commented on MSHARED-244: --- yes, commons is really good in those regards. But

[jira] (MSHARED-243) add a way to calculate diffs of a directory at 2 different times

[ https://jira.codehaus.org/browse/MSHARED-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed MSHARED-243. - Resolution: Fixed Implemented in DirectoryScanner#diffIncludedFiles( String[] oldFiles ); This

[jira] (SUREFIRE-863) NPE in ConcurrentReporterManager

[ https://jira.codehaus.org/browse/SUREFIRE-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=308764#comment-308764 ] Mark Struberg commented on SUREFIRE-863: Yes, I can try this. Just gimme a few days

[jira] (MCOMPILER-133) Facing OutOfMemory as IsolatedClassloader (plexus-compiler jar) is not closed after JavacCompiler is done with compilation.

[ https://jira.codehaus.org/browse/MCOMPILER-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=308503#comment-308503 ] Mark Struberg commented on MCOMPILER-133: - agree, setting to wont-fix

[jira] (MCOMPILER-133) Facing OutOfMemory as IsolatedClassloader (plexus-compiler jar) is not closed after JavacCompiler is done with compilation.

[ https://jira.codehaus.org/browse/MCOMPILER-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed MCOMPILER-133. --- Resolution: Won't Fix Facing OutOfMemory as IsolatedClassloader (plexus-compiler jar) is

[jira] (MSHARED-243) add a way to calculate diffs of a directory at 2 different times

Mark Struberg created MSHARED-243: - Summary: add a way to calculate diffs of a directory at 2 different times Key: MSHARED-243 URL: https://jira.codehaus.org/browse/MSHARED-243 Project: Maven Shared

[jira] (MSHARED-242) [shared-utils] improve shared utils featuers and introduce generics where possible

Mark Struberg created MSHARED-242: - Summary: [shared-utils] improve shared utils featuers and introduce generics where possible Key: MSHARED-242 URL: https://jira.codehaus.org/browse/MSHARED-242

[jira] (MSHARED-239) replace plexus-utils with maven-shared-utils

Mark Struberg created MSHARED-239: - Summary: replace plexus-utils with maven-shared-utils Key: MSHARED-239 URL: https://jira.codehaus.org/browse/MSHARED-239 Project: Maven Shared Components

[jira] (MSHARED-239) replace plexus-utils with maven-shared-utils

[ https://jira.codehaus.org/browse/MSHARED-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=307523#comment-307523 ] Mark Struberg commented on MSHARED-239: --- If you find a utility which is yet missing, then

[jira] (MSHARED-238) [DirectoryScanner] introduce a way to abort scanning if a certain criteria is met

Mark Struberg created MSHARED-238: - Summary: [DirectoryScanner] introduce a way to abort scanning if a certain criteria is met Key: MSHARED-238 URL: https://jira.codehaus.org/browse/MSHARED-238

[jira] (MSHARED-238) [DirectoryScanner] introduce a way to abort scanning if a certain criteria is met

[ https://jira.codehaus.org/browse/MSHARED-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned MSHARED-238: - Assignee: Mark Struberg [DirectoryScanner] introduce a way to abort scanning if a

[jira] (MSHARED-238) [DirectoryScanner] introduce a way to abort scanning if a certain criteria is met

[ https://jira.codehaus.org/browse/MSHARED-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=307392#comment-307392 ] Mark Struberg commented on MSHARED-238: --- Initial commit done in r1378655

[jira] (MSHARED-236) Refactor utility classes of shared components into an own utility package

[ https://jira.codehaus.org/browse/MSHARED-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated MSHARED-236: -- Attachment: MSHARED-236-krosenvold-original-work.patch Christian, as you are the original author,

[jira] (MSHARED-236) Refactor utility classes of shared components into an own utility package

Mark Struberg created MSHARED-236: - Summary: Refactor utility classes of shared components into an own utility package Key: MSHARED-236 URL: https://jira.codehaus.org/browse/MSHARED-236 Project:

[jira] (MSHARED-236) Refactor utility classes of shared components into an own utility package

[ https://jira.codehaus.org/browse/MSHARED-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned MSHARED-236: - Assignee: Mark Struberg Refactor utility classes of shared components into an own

[jira] (MSHARED-237) upgrade ApacheLicense 1.1 to 2.0 for some leftovers

Mark Struberg created MSHARED-237: - Summary: upgrade ApacheLicense 1.1 to 2.0 for some leftovers Key: MSHARED-237 URL: https://jira.codehaus.org/browse/MSHARED-237 Project: Maven Shared Components

[jira] (MSHARED-237) upgrade ApacheLicense 1.1 to 2.0 for some leftovers

[ https://jira.codehaus.org/browse/MSHARED-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned MSHARED-237: - Assignee: Mark Struberg upgrade ApacheLicense 1.1 to 2.0 for some leftovers

[jira] (MSHARED-237) upgrade ApacheLicense 1.1 to 2.0 for some leftovers

[ https://jira.codehaus.org/browse/MSHARED-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed MSHARED-237. - Resolution: Fixed Checked the prevenience and updated the license headers. All the files were forks

[jira] (MCOMPILER-21) compiler smarts

[ https://jira.codehaus.org/browse/MCOMPILER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=307127#comment-307127 ] Mark Struberg commented on MCOMPILER-21: gosh, it's even more broken. We also have

[jira] (MCOMPILER-21) compiler smarts

[ https://jira.codehaus.org/browse/MCOMPILER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated MCOMPILER-21: --- Attachment: MCOMPILER-21-v2.patch first version of an ugly hack to also get class

[jira] (MCOMPILER-21) compiler smarts

[ https://jira.codehaus.org/browse/MCOMPILER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned MCOMPILER-21: -- Assignee: Mark Struberg compiler smarts --- Key:

[jira] (MCOMPILER-21) compiler smarts

[ https://jira.codehaus.org/browse/MCOMPILER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated MCOMPILER-21: --- Priority: Major (was: Minor) compiler smarts --- Key:

[jira] (MCOMPILER-21) compiler smarts

[ https://jira.codehaus.org/browse/MCOMPILER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated MCOMPILER-21: --- Attachment: MCOMPILER-21.patch started with some ugly hacks for now. Doing proper incremental

[jira] (MCOMPILER-21) compiler smarts

[ https://jira.codehaus.org/browse/MCOMPILER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=307117#comment-307117 ] Mark Struberg commented on MCOMPILER-21: PS: the code above currently only builds with

[jira] (MRELEASE-727) release plugin uses wrong checkout directory

[ https://jira.codehaus.org/browse/MRELEASE-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=300032#comment-300032 ] Mark Struberg commented on MRELEASE-727: yes, please create a new one. Do you folks

[jira] (SCM-674) ScmFile.path should always be relative and never start with any file-separator

[ https://jira.codehaus.org/browse/SCM-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=299103#comment-299103 ] Mark Struberg commented on SCM-674: --- Be careful with this one. There might be tons of side effects

[jira] (MRELEASE-426) There is no way to specify a branch/tag/revision when performing a release

[ https://jira.codehaus.org/browse/MRELEASE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=298480#comment-298480 ] Mark Struberg commented on MRELEASE-426: Well, I only used CVS from mid 90s to early 2004

[jira] (MRELEASE-719) No error when release:prepare with an already existing scm tag

[ https://jira.codehaus.org/browse/MRELEASE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=298046#comment-298046 ] Mark Struberg commented on MRELEASE-719: I'm not worried about the additional work

[jira] (MRELEASE-705) Project directory appended twice

[ https://jira.codehaus.org/browse/MRELEASE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297972#comment-297972 ] Mark Struberg commented on MRELEASE-705: This could be a duplicate of MRELEASE-727 ,

[jira] (MRELEASE-719) No error when release:prepare with an already existing scm tag

[ https://jira.codehaus.org/browse/MRELEASE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297920#comment-297920 ] Mark Struberg commented on MRELEASE-719: right, we have 2 options a.) having

[jira] (MRELEASE-719) No error when release:prepare with an already existing scm tag

[ https://jira.codehaus.org/browse/MRELEASE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297924#comment-297924 ] Mark Struberg commented on MRELEASE-719: Well, you don't 'remove' anything from a scm.

[jira] (MRELEASE-747) Support Jazz SCM

[ https://jira.codehaus.org/browse/MRELEASE-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297927#comment-297927 ] Mark Struberg commented on MRELEASE-747: Hi! When hacking the similar stuff for

[jira] (MRELEASE-747) Support Jazz SCM

[ https://jira.codehaus.org/browse/MRELEASE-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297933#comment-297933 ] Mark Struberg commented on MRELEASE-747: ouch ^^ good catch, you are digging pretty deep

[jira] (MRELEASE-723) DCVS tagging commands should store the tag-name (or hash) in the the //project/scm/tag element.

[ https://jira.codehaus.org/browse/MRELEASE-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297757#comment-297757 ] Mark Struberg commented on MRELEASE-723: it looks to me that the String translateTagUrl

[jira] (MRELEASE-723) DCVS tagging commands should store the tag-name (or hash) in the the //project/scm/tag element.

[ https://jira.codehaus.org/browse/MRELEASE-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated MRELEASE-723: --- Attachment: testprj-svn-repo.zip This is a small sample svn repo which I use. Of course you

[jira] (MRELEASE-723) DCVS tagging commands should store the tag-name (or hash) in the the //project/scm/tag element.

[ https://jira.codehaus.org/browse/MRELEASE-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated MRELEASE-723: --- Attachment: testpr-git.zip and here comes the git repo DCVS tagging commands

[jira] (MRELEASE-723) DCVS tagging commands should store the tag-name (or hash) in the the //project/scm/tag element.

[ https://jira.codehaus.org/browse/MRELEASE-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed MRELEASE-723. -- Resolution: Fixed Fix Version/s: (was: 2.4) 2.3 fixed in r1333660.

[jira] (MRELEASE-723) DCVS tagging commands should store the tag-name (or hash) in the the //project/scm/tag element.

[ https://jira.codehaus.org/browse/MRELEASE-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297663#comment-297663 ] Mark Struberg commented on MRELEASE-723: This sounds reasonable, I'll give the patch a

[jira] (MRELEASE-723) DCVS tagging commands should store the tag-name (or hash) in the the //project/scm/tag element.

[ https://jira.codehaus.org/browse/MRELEASE-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297670#comment-297670 ] Mark Struberg commented on MRELEASE-723: I've now reviewed the patch and think we need to

  1   2   3   4   >