Github user trajano closed the pull request at:
https://github.com/apache/maven-doxia-tools/pull/2
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
GitHub user trajano opened a pull request:
https://github.com/apache/maven-plugins/pull/108
Updated dependencies
Key upgrade was the maven-invoker-plugin which prevented execution on
current version of Maven due to change from mvn.bat to mvn.cmd
Code change to
GitHub user trajano opened a pull request:
https://github.com/apache/maven-doxia-tools/pull/2
HttpURLConnectionLinkValidator
Deprecate the OnlineHTTPLinkValidator and used the HttpURLConnection to
utilize what is provided by the JDK including certificates and SSL
updates
GitHub user trajano opened a pull request:
https://github.com/apache/maven-plugins/pull/105
Added github for issue management
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/trajano/maven-plugins patch-1
Alternatively you can
Github user trajano commented on the issue:
https://github.com/apache/maven/pull/97
Awesome. does the https://github.com/apache/maven/blob/master/Jenkinsfile
also process pull requests so both non-Apache and Apache collaborators can
double check their work before sending over
Github user trajano commented on the issue:
https://github.com/apache/maven/pull/97
@bindul that's a good find, except I don't know how to access that myself
and Maven isn't listed there. One advantage of the `.travis.yml` approach is
it shows other people how to b
Github user trajano commented on the issue:
https://github.com/apache/maven/pull/97
Build is failing due to https://issues.apache.org/jira/browse/MNG-6166
after I synced with main branch
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user trajano commented on the issue:
https://github.com/apache/maven/pull/97
Going to simplify this PR to a single commit
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user trajano commented on the issue:
https://github.com/apache/maven/pull/97
I am also thinking perhaps we can simplify this by removing the other axis.
We should be able to target JDK7 as per the `README.md` and just set the JDK
to Oracle 8 before Sonar execution.
---
If
Github user trajano commented on the issue:
https://github.com/apache/maven/pull/97
@bellingard how about we have target env + jdk + etc basically a single
node then add a sonar execution. Sonar add on would also need to have a JDK
that is associated with the add on (for sonar
Github user trajano commented on the issue:
https://github.com/apache/maven/pull/97
@bellingard perhaps something can be added to
https://github.com/SonarSource/travis-build/blob/278d0a4bab4e95fb67a233e64a398757d80be8eb/lib/travis/build/addons/sonarqube.rb
so that it will have an
Github user trajano commented on the issue:
https://github.com/apache/maven/pull/97
I think I will hold off doing the SonarQube.com PR integration until I get
word from
https://github.com/SonarSource/sonarqube/pull/1362#discussion_r88762772 it is
easy enough to patch things to get
Github user trajano commented on the issue:
https://github.com/apache/maven/pull/97
Your pR link I mean.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so
Github user trajano commented on the issue:
https://github.com/apache/maven/pull/97
Btw your pull link is invalid.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user trajano commented on the issue:
https://github.com/apache/maven/pull/97
I don't understand why the coverage reports are not being built with
prepare-agent I guess it does not do multiproject too well if it is not defined
in the POM.
---
If your project is set up f
Github user trajano commented on the issue:
https://github.com/apache/maven/pull/97
SonarQube.com does not support Pull requests at the moment.
https://github.com/SonarSource/sonarqube/pull/1362#discussion_r88613462
I already tried and reverted it from
https://github.com
Github user trajano commented on a diff in the pull request:
https://github.com/apache/maven/pull/97#discussion_r88668878
--- Diff: .travis.yml ---
@@ -0,0 +1,44 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license
GitHub user trajano opened a pull request:
https://github.com/apache/maven/pull/97
.travis and SonarQube.com support
This PR provides two commits, the first one adds Travis build support.
https://travis-ci.org/trajano/maven
The second adds SonarQube support. For the
[ http://jira.codehaus.org/browse/MNGECLIPSE-39?page=all ]
Archimedes Trajano updated MNGECLIPSE-39:
-
Attachment: Property sheet.jpg
> POM editor
> --
>
> Key: MNGECLIPSE-39
> URL: http://jira.code
[ http://jira.codehaus.org/browse/MNGECLIPSE-39?page=comments#action_56221
]
Archimedes Trajano commented on MNGECLIPSE-39:
--
When I say the "Project" I mean in the "Package Explorer" view the top level
folders are the &qu
[ http://jira.codehaus.org/browse/MNGECLIPSE-39?page=comments#action_56056
]
Archimedes Trajano commented on MNGECLIPSE-39:
--
Rather than an all out form, why not just a property sheet in the Project? It
might be easier to build and probably
[ http://jira.codehaus.org/browse/MPECLIPSE-94?page=all ]
Archimedes Trajano reopened MPECLIPSE-94:
-
To be more specific, even if that parameter was set it won't do it. I read the
docs first and that setting has no effect on the unit
Unit Test resources are not put into the .classpath
---
Key: MPECLIPSE-94
URL: http://jira.codehaus.org/browse/MPECLIPSE-94
Project: maven-eclipse-plugin
Type: Bug
Versions: 1.9
Reporter: Archimedes Trajano
[ http://jira.codehaus.org/browse/MPCHANGELOG-68?page=comments#action_41745
]
Archimedes Trajano commented on MPCHANGELOG-68:
---
Found the cause
Didn't find password for CVSROOT ':pserver:[EMAIL PROTECTED]:/cvsroot/twiff'.
Execut
: Archimedes Trajano
When using changelog with SourceForge it seems to not return any entries.
Worked with Maven 1.0
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
[ http://jira.codehaus.org/browse/MAVEN-1625?page=comments#action_41540 ]
Archimedes Trajano commented on MAVEN-1625:
---
Current "Artiftact" plugin in CVS seems to work properly now. Someone might
want to remove the unused imports.
>
NoSuchMethodError when doing jar:install
Key: MPARTIFACT-54
URL: http://jira.codehaus.org/browse/MPARTIFACT-54
Project: maven-artifact-plugin
Type: Bug
Reporter: Archimedes Trajano
Fix For: 1.5.2
Update to CheckStyle 4.0-beta
-
Key: MPCHECKSTYLE-32
URL: http://jira.codehaus.org/browse/MPCHECKSTYLE-32
Project: maven-checkstyle-plugin
Type: New Feature
Versions: 2.6
Reporter: Archimedes Trajano
To allow support for
Support for Jetty 5.x
-
Key: MPJETTY-6
URL: http://jira.codehaus.org/browse/MPJETTY-6
Project: maven-jetty-plugin
Type: New Feature
Reporter: Archimedes Trajano
Is it possible for us to provide a property that would allow us to use jetty 5
Hibernate 3.0-rc1
-
Key: MAVENUPLOAD-317
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-317
Project: maven-upload-requests
Type: Task
Reporter: Archimedes Trajano
bundle is attached
http://www.hibernate.org
--
This message is
30 matches
Mail list logo
