Jonkman Microblog
  • Login
Show Navigation

  • Public

    • Public
    • Network
    • Groups
    • Popular
    • People

Notices by musicman (musicman@nu.federati.net), page 28

  1. musicman (musicman@nu.federati.net)'s status on Thursday, 15-Oct-2020 10:51:29 EDT musicman musicman
    in reply to
    • musicman
    just calculating the WSO2 dependency tree takes 22.614 s.

    For comparison, the dependency tree calculation for the Jenkins plugin (which I believe includes all of Jenkins) is 5.024 s.

    At some level, modules are definitely better, but I do feel like I am building an entire skyscraper to test the ice maker in the penthouse.
    In conversation Thursday, 15-Oct-2020 10:51:29 EDT from nu.federati.net permalink
  2. musicman (musicman@nu.federati.net)'s status on Thursday, 15-Oct-2020 10:45:29 EDT musicman musicman
    In a way, it's good that the WSO2 pm file is ~1400 lines long, as it means (maybe?) that it isn't hiding all of those in other dependent poms, but...yikes.
    In conversation Thursday, 15-Oct-2020 10:45:29 EDT from nu.federati.net permalink
  3. musicman (musicman@nu.federati.net)'s status on Thursday, 15-Oct-2020 10:05:01 EDT musicman musicman
    in reply to
    • musicman
    I guess strictly speaking that remains to be seen, but it has been a while...
    In conversation Thursday, 15-Oct-2020 10:05:01 EDT from nu.federati.net permalink
  4. musicman (musicman@nu.federati.net)'s status on Thursday, 15-Oct-2020 10:04:36 EDT musicman musicman
    in reply to
    • musicman
    well, it certainly isn't any faster...
    In conversation Thursday, 15-Oct-2020 10:04:36 EDT from nu.federati.net permalink
  5. musicman (musicman@nu.federati.net)'s status on Thursday, 15-Oct-2020 08:50:21 EDT musicman musicman
    according to https://www.yenlo.com/blog/building-wso2-products-from-source-2.0

    mvn clean install

    is the way to go.

    We shall see. We. shall. see.
    In conversation Thursday, 15-Oct-2020 08:50:21 EDT from nu.federati.net permalink

    Attachments

    1. Invalid filename.
      Building WSO2 products from source 2.0
      In this blog we'll provide some insight into the WSO2 source code structure. If you are planning on building WSO2 products you will require 3 applications: a Git client to obtain the source code, a Java8 JDK and Maven to compile the source code.
  6. musicman (musicman@nu.federati.net)'s status on Thursday, 15-Oct-2020 08:25:11 EDT musicman musicman
    in reply to
    • musicman
    at least the compile failed much more quickly, but I wish they would say something other than build at the end:

    [INFO] WSO2 API Manager - Based on product backend Test Module FAILURE [ 11.253 s]
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 04:11 min
    [INFO] Finished at: 2020-10-14T17:01:43-05:00
    [INFO] ------------------------------------------------------------------------
    [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.1.1:unpack (unpack-mar-jks) on project org.wso2.carbon.am.integration.backend.test: Unable to find/resolve artifact.: Could not find artifact org.wso2.am:wso2am:zip:3.2.0 in repo.jenkins-ci.org (https://repo.jenkins-ci.org/public/) -> [Help 1]
    In conversation Thursday, 15-Oct-2020 08:25:11 EDT from nu.federati.net permalink
  7. musicman (musicman@nu.federati.net)'s status on Thursday, 15-Oct-2020 08:22:14 EDT musicman musicman
    in reply to
    • musicman
    [INFO] WSO2 API Manager - Based on product backend Test Module FAILURE [ 02:22 h]
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 02:58 h
    In conversation Thursday, 15-Oct-2020 08:22:14 EDT from nu.federati.net permalink
  8. musicman (musicman@nu.federati.net)'s status on Wednesday, 14-Oct-2020 18:01:33 EDT musicman musicman
    in reply to
    • musicman
    well, maybe one of these will be done by morning...
    In conversation Wednesday, 14-Oct-2020 18:01:33 EDT from nu.federati.net permalink
  9. musicman (musicman@nu.federati.net)'s status on Wednesday, 14-Oct-2020 17:58:07 EDT musicman musicman
    in reply to
    • musicman
    idk what compile does versus package, but gonna give that a go...
    In conversation Wednesday, 14-Oct-2020 17:58:07 EDT from nu.federati.net permalink
  10. musicman (musicman@nu.federati.net)'s status on Wednesday, 14-Oct-2020 17:40:31 EDT musicman musicman
    in reply to
    • musicman
    well, there goes that plan:

    Unknown lifecycle phase "build". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>.
    In conversation Wednesday, 14-Oct-2020 17:40:31 EDT from nu.federati.net permalink
  11. musicman (musicman@nu.federati.net)'s status on Wednesday, 14-Oct-2020 17:39:04 EDT musicman musicman
    in reply to
    • musicman
    tempted to run mvn build in another terminal tab, but I have a feeling that is a bad idea. I guess I could do it in a different directory...
    In conversation Wednesday, 14-Oct-2020 17:39:04 EDT from nu.federati.net permalink
  12. musicman (musicman@nu.federati.net)'s status on Wednesday, 14-Oct-2020 17:37:13 EDT musicman musicman
    in reply to
    • musicman
    ok, and then it turned itself off, again...I guess going through an entire test suite. I'm no maven guru, but I've run maven enough to feel this is super weird. I mean, I was complaining about this taking a long time an hour ago...

    I wonder if I should have used build instead of package...
    In conversation Wednesday, 14-Oct-2020 17:37:13 EDT from nu.federati.net permalink
  13. musicman (musicman@nu.federati.net)'s status on Wednesday, 14-Oct-2020 17:36:45 EDT musicman musicman
    in reply to
    • musicman
    ok, and then it turned itself off, again...I guess going through an entire test suite. I'm no maven guru, but I've run maven enough to feel this is super weird. I mean, I was complaining about this taking a long time 54 minutes ago...
    In conversation Wednesday, 14-Oct-2020 17:36:45 EDT from nu.federati.net permalink
  14. musicman (musicman@nu.federati.net)'s status on Wednesday, 14-Oct-2020 17:33:27 EDT musicman musicman
    in reply to
    • musicman
    ok, we're working, but unclear if this is "built" such that I can turn it back on later. Like, is mvn ever going to say it is done?
    In conversation Wednesday, 14-Oct-2020 17:33:27 EDT from nu.federati.net permalink
  15. musicman (musicman@nu.federati.net)'s status on Wednesday, 14-Oct-2020 17:29:29 EDT musicman musicman
    in reply to
    • musicman
    hmm, been doing this a bit:
    INFO [org.wso2.carbon.integration.common.utils.ClientConnectionUtil] - Waiting until server starts on port 9943
    In conversation Wednesday, 14-Oct-2020 17:29:29 EDT from nu.federati.net permalink
  16. musicman (musicman@nu.federati.net)'s status on Wednesday, 14-Oct-2020 17:15:48 EDT musicman musicman
    in reply to
    • musicman
    I think it is running an entire test suite now, which I guess is cool, but not something I have seen other projects do.
    In conversation Wednesday, 14-Oct-2020 17:15:48 EDT from nu.federati.net permalink
  17. musicman (musicman@nu.federati.net)'s status on Wednesday, 14-Oct-2020 16:38:08 EDT musicman musicman
    in reply to
    • musicman
    pausing music and going to turn on an instructional video. A sure sign the compile is about to end.
    In conversation Wednesday, 14-Oct-2020 16:38:08 EDT from nu.federati.net permalink
  18. musicman (musicman@nu.federati.net)'s status on Wednesday, 14-Oct-2020 16:35:07 EDT musicman musicman
    in reply to
    • musicman
    I should really get in the habit of running the time command with compiles because i am definitely in the wtf stage. I think Maven will print out a time though....eventually.
    In conversation Wednesday, 14-Oct-2020 16:35:07 EDT from nu.federati.net permalink
  19. musicman (musicman@nu.federati.net)'s status on Wednesday, 14-Oct-2020 16:33:43 EDT musicman musicman
    So, um, are these referencing 14 and 15 or 1.4 and 1.5...

    <profiles>
    <profile>
    <id>jdk14</id>
    <activation>
    <jdk>1.4</jdk>
    </activation>
    <dependencies>
    <dependency>
    <groupId>bouncycastle</groupId>
    <artifactId>bcprov-jdk13</artifactId>
    <version>${bcprov.jdk13.version}</version>
    </dependency>
    </dependencies>
    </profile>

    <profile>
    <id>jdk15</id>
    <activation>
    <activeByDefault>true</activeByDefault>
    <jdk>1.5</jdk>
    </activation>
    <dependencies>
    <dependency>
    <groupId>bouncycastle</groupId>
    <artifactId>bcprov-jdk15</artifactId>
    <version>${bcprov.jdk15.version}</version>
    </dependency>
    </dependencies>
    </profile>
    In conversation Wednesday, 14-Oct-2020 16:33:43 EDT from nu.federati.net permalink
  20. musicman (musicman@nu.federati.net)'s status on Wednesday, 14-Oct-2020 16:24:10 EDT musicman musicman
    in reply to
    • lnxw48a1
    fair enough.
    In conversation Wednesday, 14-Oct-2020 16:24:10 EDT from nu.federati.net permalink
  • After
  • Before
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

Jonkman Microblog is a social network, courtesy of SOBAC Microcomputer Services. It runs on GNU social, version 1.2.0-beta5, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All Jonkman Microblog content and data are available under the Creative Commons Attribution 3.0 license.

Switch to desktop site layout.