oject:
Maven 2.x JBoss Plugin
Priority:
Major
Reporter:
Mark H
[
https://jira.codehaus.org/browse/MOJO-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson closed MOJO-1702.
-
Resolution: Fixed
Expanded frames rather than skip them during Apt class transformation to pass
Java7
[
https://jira.codehaus.org/browse/MOJO-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292431#comment-292431
]
Mark Hobson commented on MOJO-1702:
---
This appears to be due to changes in Java 7 that req
[
https://jira.codehaus.org/browse/MOJO-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson updated MOJO-1702:
--
Affects Version/s: apt-maven-plugin-1.0-alpha-4
Fix Version/s: apt-maven-plugin-1.0-alpha-5
[
https://jira.codehaus.org/browse/MOJO-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson reassigned MOJO-1702:
-
Assignee: Mark Hobson
> apt plugin fails when running on jav
Hi Dan,
Looks like the plugins list wasn't updated for the release. I've
moved it to 3.0, corrected the link and deployed the site.
Cheers,
Mark
On 6 February 2012 20:34, Dan Tran wrote:
> Hi,
>
> The Mojo team is pleased to announce the release of the Maven
> Hibernate 3 Plugin version 3.0
>
[
https://jira.codehaus.org/browse/MOJO-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson closed MOJO-1609.
-
Resolution: Fixed
Fix Version/s: apt-maven-plugin-1.0-alpha-5
Patched applied in r14641, thanks
[
https://jira.codehaus.org/browse/MOJO-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson reassigned MOJO-1609:
-
Assignee: Mark Hobson
> EclipseMojo creates factory path entries with trailing whitesp
ing for Mark (id : thragor).
>> So I ask you have a look here [1] in order to provide the necessary
>> cla material (if any issue contact me)
>>
>> Thanks,
>> --
>> Olivier Lamy
>> http://twitter.com/olamy
>> http://www.linkedin.com/in/olamy
>>
[
https://jira.codehaus.org/browse/MTOMCAT-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=273887#comment-273887
]
Mark Hobson commented on MTOMCAT-93:
A vote was started on mojo-dev:
http://markmail
Move tomcat-maven-plugin to Apache Tomcat
-
Key: MTOMCAT-93
URL: https://jira.codehaus.org/browse/MTOMCAT-93
Project: Maven 2.x Tomcat Plugin
Issue Type: Task
Reporter: Mark Hobson
On 24 January 2011 13:50, Olivier Lamy wrote:
> Hi Folks,
>
> In order to resolve some trademarks issues with the mojo name, I'd
> like to move the tomcat-maven-plugin to Apache Tomcat project.
> The second reason is : IMHO it's probably the best and more natural
> place for this to be hosted.
> I
The Mojo team is pleased to announce the release of the Apt Maven
Plugin, version 1.0-alpha-4.
This plugin provides goals to run the Annotation Processing Tool (apt)
against project sources.
http://mojo.codehaus.org/apt-maven-plugin/
You should specify the version in your project's plugin config
Vote has passed by lazy consensus. I'll now promote the artifacts.
Mark
On 16 September 2010 17:13, Mark Hobson wrote:
> Hi,
>
> We solved 3 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11062&version=16158
>
> There are still a couple of
On 17 September 2010 17:54, Robert Scholte wrote:
> This is weird: mojo-parent[1] uses maven-checkstyle-plugin:2.5 in the
> build-section, but 2.2 in the reporting-section.
> These should be the same and would explain the problem.
>
> [1] http://svn.codehaus.org/mojo/trunk/mojo/mojo-parent/pom.xml
On 17 September 2010 12:08, Benjamin Bentmann wrote:
> expression="" is meant for system properties the user can specify on the CLI
> and nothing else (MNG-2063). Fetching values from the project and other
> sources should happen via default-value, independently from the question
> whether those v
Robert,
On 16 September 2010 21:38, Robert Scholte wrote:
> Mark,
>
> right now I see a bit too much issues to give it a +1.
>
> here are a few of my remarks, purely based on code and sitedocs
> - check http://mojo.codehaus.org/apt-maven-plugin/checkstyle.html : 300+
> errors is really too much.
On 16 September 2010 19:57, Robert Scholte wrote:
> Since you did it pretty recently, I'd suggest you add it yourself.
> I have tried to complete everything considering the staging-stuff, but this
> certificate-stuff is something I'd done months ago.
> But this is also an *only once* thing which h
Hi there,
Was anyone planning on updating the release documentation [1] for the
new SSL certificates [2]? I discovered [3] that we now need to import
certificates in order to deploy sites successfully.
Mark
[1] http://mojo.codehaus.org/development/performing-a-release.html
[2] https://docs.code
Hi,
We solved 3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11062&version=16158
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MOJO+AND+component+%3D+apt+AND+status+%3D+Open+ORDER+BY+prior
Hi Benjamin,
On 15 September 2010 17:29, Benjamin Bentmann wrote:
> Maybe I miss something but won't the removal of provided and in particular
> system scope potentially break the plugin?
Potentially, if someone uses a provided or system scoped processor
dependency, which would just be weird. T
[
http://jira.codehaus.org/browse/MOJO-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson closed MOJO-1570.
-
Resolution: Fixed
Fixed in r12564.
> [m3] Apt fails to include plugin dependencies in classp
[
http://jira.codehaus.org/browse/MOJO-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson updated MOJO-1570:
--
Fix Version/s: apt-maven-plugin-1.0-alpha-4
Assignee: Mark Hobson
> [m3] Apt fails to include plu
Affects Versions: apt-maven-plugin-1.0-alpha-3
Reporter: Mark Hobson
MNG-4761 in Maven 3.0.0-beta-3 means that plugin dependencies are automatically
upgraded to runtime scope and are thus not added to the compile classpath when
running apt.
Need to include compile and runtime plugin
[
http://jira.codehaus.org/browse/MOJO-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson closed MOJO-1494.
-
Resolution: Fixed
Only added source and resource directories if they haven't been added already.
> So
[
http://jira.codehaus.org/browse/MTOMCAT-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210692#action_210692
]
Mark Hobson commented on MTOMCAT-4:
---
In my example I was using the default final name, hence
[
http://jira.codehaus.org/browse/MTOMCAT-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210683#action_210683
]
Mark Hobson commented on MTOMCAT-4:
---
The main reason was to simplify the URL when accessing
Issue Type: Bug
Components: apt
Affects Versions: apt-maven-plugin-1.0-alpha-1
Reporter: Mark Hobson
We need to check whether we've already added source and resource directories
before adding them.
--
This message is automatically generated by JIRA.
-
If you think i
[
http://jira.codehaus.org/browse/MOJO-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson updated MOJO-1494:
--
Fix Version/s: apt-maven-plugin-1.0-alpha-4
Assignee: Mark Hobson
> Source and resource dirs
[
http://jira.codehaus.org/browse/MOJO-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson closed MOJO-1478.
-
Resolution: Fixed
Hopefully now resolved by separating {{-d}} and {{-s}} paths:
* {{outputDirectory}} now sets
[
http://jira.codehaus.org/browse/MOJO-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson updated MOJO-1478:
--
Affects Version/s: apt-maven-plugin-1.0-alpha-2
Fix Version/s: apt-maven-plugin-1.0-alpha-4
[
http://jira.codehaus.org/browse/MTOMCAT-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson closed MTOMCAT-49.
--
> Goal tomcat:run fails
> -
>
> Key: MTOMCAT-49
>
[
http://jira.codehaus.org/browse/MTOMCAT-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson resolved MTOMCAT-49.
Resolution: Not A Bug
> Goal tomcat:run fails
> -
>
>
[
http://jira.codehaus.org/browse/MTOMCAT-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson reopened MTOMCAT-49:
> Goal tomcat:run fails
> -
>
> Key: MTOMCAT-49
>
2010/1/13 Peter Lynch :
> Mark, I ran the apt plugin with java 5 and 6 on OSX with your changes and
> all works well - tests pass. I also tested it on my other project. No
> problems. The only caveat is I can't seem to reproduce the original bug
> reliably so have no way of knowing If I will ever s
2010/1/11 Mark Hobson :
> Sure, for (1) we'd also need to change the tests to use CLASS_TREE
> instead of SOURCE_TREE, which does pass locally. I'll add a unit test
> to exercise the -s sourceOutputDirectory option in conjunction with
> SOURCE_TREE for (3).
>
> I&
[
http://jira.codehaus.org/browse/MOJO-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson updated MOJO-1478:
--
Summary: Distinguish between -d and -s correctly when invoking apt (was:
apt -s does not work reliably
[
http://jira.codehaus.org/browse/MOJO-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson reassigned MOJO-1478:
-
Assignee: Mark Hobson
> apt -s does not work reliably, should be
2010/1/11 Peter Lynch :
> Re 1, no. Just changing -s to -d fails 16 unit tests on my system - just
> confirmed. Keeping -s and -d pointing to same directory does work fine ( as
> in patch). It seems both must be set - or perhaps I am being fooled since
> just -s is working at the moment too - ugh.
of the 18 existing integration tests will fail if the bug appears
> anyways.
>
> Given the above, perhaps consider applying the patch and taking our chances?
>
> -Peter
>
> On Mon, Jan 11, 2010 at 10:42 AM, Mark Hobson wrote:
>>
>> Ryan, what environment were you using i
Ryan, what environment were you using in that stack trace you posted?
(OS, JVM, Maven.)
Mark
2010/1/6 Mark Hobson :
> How strange, thanks for retrying Peter. I'd rather not apply a patch
> without it demonstrably fixing something as it just confuses the code.
>
> Cheers,
>
[
http://jira.codehaus.org/browse/MOJO-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206443#action_206443
]
Mark Hobson commented on MOJO-1478:
---
Let's continue diagnosing this on the mailing list
[
http://jira.codehaus.org/browse/MOJO-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206380#action_206380
]
Mark Hobson commented on MOJO-1478:
---
I've just run the apt-maven-plugin tests under Java
[
http://jira.codehaus.org/browse/MOJO-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206203#action_206203
]
Mark Hobson commented on MOJO-1478:
---
I'd love to reproduce this, can anyone supply a pro
any changes. This is really weird. Although I
> think the patch is harmless, I'll mark the issue as Closed, can't reproduce.
>
> Thanks.
>
> On Tue, Jan 5, 2010 at 4:31 PM, Mark Hobson wrote:
>>
>> Hi Peter,
>>
>> Apologies for the late reply. I&#x
help.
>
> -Peter
>
> On Thu, Dec 17, 2009 at 5:09 AM, Mark Hobson wrote:
>>
>> Hi Peter,
>>
>> I've never had a problem with apt generating resources in the wrong
>> directory. Can you attach an example test project to demonstrate the
>> p
The Mojo team is pleased to announce the first release of the Batik
Maven Plugin, version 1.0-beta-1.
This plugin rasterizes SVGs using Apache Batik.
http://mojo.codehaus.org/batik-maven-plugin/
You should specify the version in your project's plugin configuration:
org.codehaus.mojo
batik-ma
The vote has passed by lazy consensus:
+1: Stephen Connolly
I'll proceed with graduating the plugin.
Cheers,
Mark
2009/12/16 Stephen Connolly :
> +1 early & often
>
> -Stephen
>
> 2009/12/16 Mark Hobson
>>
>> Hi there,
>>
>> I'd like to g
Hi Peter,
I've never had a problem with apt generating resources in the wrong
directory. Can you attach an example test project to demonstrate the
problem here?
Cheers,
Mark
2009/12/17 Peter Lynch :
> Hi,
>
> I created jira http://jira.codehaus.org/browse/MOJO-1478 and provided the
> patch to
Hi there,
I'd like to graduate the batik-maven-plugin out of the sandbox and
make a first 1.0-beta-1 release.
The site has been deployed to:
http://mojo.codehaus.org/batik-maven-plugin/
The project source can be found at:
http://svn.codehaus.org/mojo/trunk/sandbox/batik-maven-plugin/
The vote
Upgrade Tomcat to 6.0.20
Key: MTOMCAT-41
URL: http://jira.codehaus.org/browse/MTOMCAT-41
Project: Maven 2.x Tomcat Plugin
Issue Type: Improvement
Affects Versions: 1.0-beta-1
Reporter: Mark Hobson
Just caught up with my emails and saw MOJO-1458, awesome work
Benjamin! That's been on my todo list for some time now. Should also
fix MNGECLIPSE-1294 which means apt-maven-plugin is now m2eclipse
compatible :)
Thanks,
Mark
2009/11/25 Benjamin Bentmann :
> The Mojo team is pleased to announce
[
http://jira.codehaus.org/browse/MHIBERNATE-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199431#action_199431
]
Mark Hobson commented on MHIBERNATE-93:
---
Any chance of backporting this to 2.x? D
2009/8/25 Dan Tran :
> Mojo team,
>
> I would like to cut second alpha release for properties-maven-plugin,
> which contains the following fixes:
>
>
> [MOJO-1369] Add goal to set system properties
>
> [MOJO-1327]:allow system properties to overwrite maven properties.
>
>
> Snapshot and site have b
rnate Plugin
Issue Type: Improvement
Affects Versions: 2.2
Reporter: Mark Hobson
Assignee: Johann Reyes
All goals currently create a classloader consisting of the project's
compile-scoped dependencies. We should really include runtime-scoped
dependenc
2009/5/25 :
> System (as in OS) properties are available as normal variables, with a
> prefix ENV, so for example this expression:
> ${ENV.HOME} would resolve the $HOME variable.
Sure, but this is to set Java system properties as part of the build process.
Mark
-
2009/5/22 Paul Gier :
> I think the location for maven_checks.xml is good, but is
> "config/maven-header.txt" a predefined file in the checkstyle plugin? If
> not, maybe it would be better to just leave that location blank and use the
> default "LICENSE.txt".
>
> wdyt?
Yep, it's a standard resour
2009/5/22 Stephen Connolly :
> we should see about calling a vote as it will block any other mojo releases
> until parent is released
Sure, unless people want to check the deployed snapshot first? It
worked for me though.
Mark
2009/5/20 Mark Hobson :
> Sounds good to me. I'll commit and deploy one if I hear no objections.
Committed in r9759 and deployed mojo-parent 21-SNAPSHOT. Let me know
if there's any problems.
I'll also post to maven-dev since there's a similar issue
2009/5/20 Garvin LeClaire :
> I am fine with option 3.
>
> I read in the post that this will involve a new version of the mojo-parent
> and we will need to change our plugin POMs accordingly once the new parent
> is released?
That's right.
> We should release a SNAPSHOT parent for plugins experie
r wrote:
>> I would say add it to either the properties-maven-plugin or
>> buildhelper-maven-plugin. Since it seems like a simple task to have a full
>> plugin. But either way is probably fine.
>>
>> Mark Hobson wrote:
>>>
>>> Hi there,
>>>
[
http://jira.codehaus.org/browse/MOJO-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson closed MOJO-1369.
-
Assignee: Mark Hobson
Resolution: Fixed
Added properties:set-system-properties goal to trunk (1.0-alpha-2
Add goal to set system properties
-
Key: MOJO-1369
URL: http://jira.codehaus.org/browse/MOJO-1369
Project: Mojo
Issue Type: New Feature
Components: properties
Reporter: Mark Hobson
Hi there,
The mojo-parent Checkstyle configuration [1] uses the JavadocPackage
check, which is new in 5.0, but the POM specifies
maven-checkstyle-plugin 2.2 which uses Checkstyle 4.4. This means
that site generation fails for any plugin that uses this parent.
MCHECKSTYLE-105 introduced the Check
-beta-1
Reporter: Mark Hobson
Priority: Minor
Fix For: 1.0
Conventionally, code can use the current thread's context class loader to load
classes. This is not set in the run and run-war goals leading to potential
ClassNotFoundExceptions. We should s
Hi there,
I have a need to set a system property as part of a build without
using CLI options. AFAIK there is no way to do this natively within
the POM, so I'm proposing a new goal and/or plugin.
I can either add this to the sandbox as a new plugin
(sysprop-maven-plugin?) or add it as another go
2009/4/16 Stephen Connolly :
> except from our point of view (i.e. the versions maven plugin) the use
> of :version may be problematic...
How come? Omitting version would match all versions.
> I'm thinking
>
> gID:aID:type:classifier:version
I'd be all for introducing classifier into the syntax
2009/4/16 Stephen Connolly :
> I've no issues with using excludes and not exclude
>
> of course the big issue I see is that all the goals in
> maven-dependency-plugin have different properties doing exactly the
> same thing!
>
> I have to say I like your syntax, as gives a way to specify a complete
2009/4/16 Stephen Connolly :
> when writing a mojo that acts on dependencies which is the nicer
> way to handle includes and excludes
> dependency:purge-local-repository has a
> -Dexclude=groupId:artifactId,groupId:artifactId style
> while
> dependency:copy-dependencies has a -DexcludeGroupIds=
Sounds like a handy goal. A few more checks that would be handy until
we have usable version ranges:
- Warn if an artifact's version resolves to a version lower than one
specified in a transitive pom (i.e. a dependency is being downgraded
because it is nearest)
- As above, but also comparing aga
[
http://jira.codehaus.org/browse/MTOMCAT-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171103#action_171103
]
Mark Hobson commented on MTOMCAT-3:
---
Could you raise another issue for that please since this
2009/1/21 Olivier Lamy :
> I'd just like to review license headers and try to fix last checkstyle issues.
Cool, probably best to call another vote once that's done.
Thanks,
Mark
-
To unsubscribe from this list, please visit:
Really? I think it far too verbose during day to day development. If
one is having dependency problems then running with -X isn't too much
of a problem. What do you think?
Mark
2009/1/21 Olivier Lamy :
> As we don't have the WEB-INF/lib to see dependencies, personnally I
> like the info level
2009/1/20 Olivier Lamy :
> Hi,
>
> I would like to call a vote for a 1.0-alpha-1 release of the
> tomcat-maven-plugin
>
> The site is at http://mojo.codehaus.org/tomcat-maven-plugin/
> The release note is here :
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14909&styleName=Text&projec
2009/1/21 Olivier Lamy :
> Hi,
> There are some checkstyle errors due to the license header.
> This header has your name. Can we remove this and use a strict apache
> license header ?
Sure, please feel free to update them. They were in line with the
standards when I wrote the plugin way back in 2
[
http://jira.codehaus.org/browse/MOJO-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156284#action_156284
]
Mark Hobson commented on MOJO-594:
--
I'd like to see another release of the plugin soon, b
Affects Versions: 1.0
Environment: Windows XP, Cygwin, Maven 2.0.9, Java 1.5.0_16
Reporter: Mark Hobson
Priority: Blocker
Running {{gwt:compile}} under Windows with the default local repository
location, which has spaces in, results in:
{noformat
[
http://jira.codehaus.org/browse/MOJO-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson closed MOJO-1032.
-
Resolution: Fixed
> Not failing when trying to undeploy applicat
[
http://jira.codehaus.org/browse/MOJO-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151736#action_151736
]
Mark Hobson commented on MOJO-1032:
---
Applied patch with modifications thanks. I renamed
[
http://jira.codehaus.org/browse/MOJO-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151650#action_151650
]
Mark Hobson commented on MOJO-1032:
---
I'll try to find some time to review and apply the p
[
http://jira.codehaus.org/browse/MOJO-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson closed MOJO-1240.
-
Resolution: Duplicate
> Implemention of som nice features: run multiple war file, setup tom
[
http://jira.codehaus.org/browse/MOJO-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150164#action_150164
]
Mark Hobson commented on MOJO-1240:
---
Thanks Sandro. There appears to be no patch for MOJO-1241
[
http://jira.codehaus.org/browse/MOJO-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson reassigned MOJO-1241:
-
Assignee: Mark Hobson
> multi warfile support in tomcat:run g
[
http://jira.codehaus.org/browse/MOJO-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson reassigned MOJO-1242:
-
Assignee: Mark Hobson
> additional tomcat config files support in tomcat:run g
[
http://jira.codehaus.org/browse/MOJO-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson reassigned MOJO-1240:
-
Assignee: Mark Hobson
> Implemention of som nice features: run multiple war file, setup tom
[
http://jira.codehaus.org/browse/MOJO-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150051#action_150051
]
Mark Hobson commented on MOJO-1240:
---
If you could please, it makes it easier to manage. I
[
http://jira.codehaus.org/browse/MOJO-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150028#action_150028
]
Mark Hobson commented on MOJO-1240:
---
Could you split this patch up as follows please:
1) Op
[
http://jira.codehaus.org/browse/MOJO-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson closed MOJO-1225.
-
Assignee: Mark Hobson
Resolution: Duplicate
Duplicated by MOJO-1106, fixed in trunk.
> Upgrade tom
[
http://jira.codehaus.org/browse/MOJO-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148679#action_148679
]
Mark Hobson commented on MOJO-1106:
---
James, the patch has been applied to trunk, so you just
2008/9/2 Stephen Connolly <[EMAIL PROTECTED]>:
> Any chance we could add an [EMAIL PROTECTED] and move all the jira
> mails to that list so that the Signal to Noise Ration for the dev list is
> not quite so full of issues?
Signal to Noise Ration? ;)
+1
Mark
-
[
http://jira.codehaus.org/browse/MOJO-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145128#action_145128
]
Mark Hobson commented on MOJO-928:
--
A related plugin has emerged in the sandbox, you ma
[
http://jira.codehaus.org/browse/MOJO-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson closed MOJO-1142.
-
Resolution: Cannot Reproduce
Closing this as I cannot reproduce the problem. Please reopen and attach a
test
[
http://jira.codehaus.org/browse/MOJO-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson closed MOJO-818.
Resolution: Fixed
This is essentially fixed by MOJO-1106 since Tomcat 6 no longer uses JCL. I've
now remove
[
http://jira.codehaus.org/browse/MOJO-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson closed MOJO-594.
Resolution: Fixed
Thanks for the patch, although I ended up implementing this by configuring the
context directly
[
http://jira.codehaus.org/browse/MOJO-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson closed MOJO-1181.
-
Assignee: Mark Hobson
Resolution: Fixed
> Change default web context to artifact id for run go
[
http://jira.codehaus.org/browse/MOJO-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson closed MOJO-1106.
-
Resolution: Fixed
Applied patch with slight modifications, thanks.
tomcat:run and tomcat:run-war now both use
Reporter: Mark Hobson
Priority: Minor
Currently the default web context is the artifact's final name which by default
is artifactId-version. It'd be better to default to the artifact id instead,
as per jetty's plugin.
--
This message is automatically ge
[
http://jira.codehaus.org/browse/MOJO-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson updated MOJO-735:
-
Attachment: MOJO-735b.patch
Oops, uploading second version of MOJO-735b.patch, this time without
it10/target
[
http://jira.codehaus.org/browse/MOJO-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson closed MOJO-1151.
-
Assignee: Mark Hobson (was: Jochen Wiedmann)
Resolution: Fixed
This was fixed in r7244 by using
[
http://jira.codehaus.org/browse/MOJO-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson reopened MOJO-740:
--
Input XMLs are not validated when transformationSet.validating=true in the
current trunk.
> Allow input XML
1 - 100 of 234 matches
Mail list logo
